Home › Forums › Developers › General developer's discussion ›

[OpenVPMS Developers] [JIRA] Created: (OVPMS-928) replacing a breed lookup does not update the patient's description.

Submitted by tony on Fri, 12/02/2010 - 22:00
in
replacing a breed lookup does not update the patient's description. --------------------------------------------------------------------

Key: OVPMS-928 URL: https://openvpms.atlassian.net/browse/OVPMS-928 Project: VPMS Web Application Issue Type: Bug Affects Versions: 1.4-beta-1 Reporter: Matthew Young Assignee: Tony De Keizer Priority: Minor

If a breed lookup is replaced, the patient description displayed in the application does not update to the new breed, it remains as it previously was. To get it to update you need to edit and change the breed.

-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://openvpms.atlassian.net/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

_______________________________________________ OpenVPMS Developers Mailing List developers@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/listinfo/developers Posts from this mailing list can be viewed online and replied to in the OpenVPMS Developer's forum- http://tinyurl.com/openvdf

‹ [OpenVPMS Developers] [JIRA] Created: (OVPMS-929) Reminder Workspace not processing second and subsequent reminders [OpenVPMS Developers] [JIRA] Created: (REL-9) archload script won't run. ›

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

[OpenVPMS Developers] [JIRA] Commented: (OVPMS-928) replacing a

Submitted by tony on Sun, 14/02/2010 - 12:00.
[ https://openvpms.atlassian.net/browse/OVPMS-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11884#action_11884 ]

Tim Anderson commented on OVPMS-928: ------------------------------------

This is true of any lookup editing. i.e if you edit a lookup, the changes won't propagate to the objects that refer to it. For this to occur, a search would need to be performed to: # find all archetypes that refer to the lookup (by its archetype) # for each archetype referring to the lookup, find all objects # evaluate all derived fields for the object # save the object if any of the derived fields has changed

All derived fields need to be updated, as its not possible to determine which derived field refers to a lookup.

However, this may yield unexpected or undesirable behaviour. e.g if a derived node has a timestamp, this will be re-evaluated. I don't know of any archetype that would be affected by this at present, but may be a problem in future

> replacing a breed lookup does not update the patient's description. > -------------------------------------------------------------------- > > Key: OVPMS-928 > URL: https://openvpms.atlassian.net/browse/OVPMS-928 > Project: VPMS Web Application > Issue Type: Bug > Affects Versions: 1.4-beta-1 > Reporter: Matthew Young > Assignee: Tony De Keizer > Priority: Minor > > If a breed lookup is replaced, the patient description displayed in the application does not update to the new breed, it remains as it previously was. To get it to update you need to edit and change the breed.

-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://openvpms.atlassian.net/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

_______________________________________________ OpenVPMS Developers Mailing List developers@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/listinfo/developers Posts from this mailing list can be viewed online and replied to in the OpenVPMS Developer's forum- http://tinyurl.com/openvdf

Syndicate content