Filter duplicate relationships when replacing one lookup with another ---------------------------------------------------------------------

Key: OVPMS-1078 URL: https://openvpms.atlassian.net/browse/OVPMS-1078 Project: VPMS Web Application Issue Type: Improvement Reporter: Tim Anderson Assignee: Tony De Keizer Priority: Minor

OVPMS-1062 added support to copy lookup relationships from the original to the replacing lookup when performing lookup replacement, with the caveat that duplicate relationships would not be filtered. This JIRA is to: * move relationships from the original to the replacing lookup, to avoid validation errors * filter duplicate relationships

This will enable operations like: # replacing a breed with another where both have the same species relationship # replacing one lookup.state with another, moving the original state's suburbs to the replacing lookup

Note that replacement won't be supported where the original lookup is a target of a different lookup to that of the replacing lookup - this will fail with a validation error. E.g, it won't be possible to replace a feline breed with a canine one, as the species is different.

-- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://openvpms.atlassian.net/secure/ContactAdministrators!default.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