We are in the process of upgrading from system from Ent10.8.1, AGP2.7.4, UN3 to Ent 11.1, AGP3.2 (or greater) and UNM6.
One of our workflows, when setting associations, users will typically do a broader select to update associations, trusting the system to make the appropriate selection, based on our configured rules, then review and apply. In AGP2.7.4 this can handle where an association already exists and only apply the changes. In AGP3.2 (and proven back in AGP2.9) users receive an error if an association already exists, and the modify associations pane shows the duplicate entry (shown below)
User receives an error message when pressing apply. This error remains until the user removes the duplicate record.
Is this expected behaviour? Surely the tool can handle checking if the association exists or not like it does in AGP2.7.4.
