Trying to merge an agent that includes one of the agents in the merge as a related agent causes database integrity constraint conflict

Miloche's reply:
I am able to merge agents with agent links that don't include agents directly involved in the merge.
So the issue is probable because the merged records were linked to each other.

Thanks and ! Sounds like we need a check that a related agent isn't also one of the agents that's part of the merge, but that's thankfully a narrower issue to address.

this was discussed in Dev. Pri. how would you see the resolution to this, we will need it before being able to prioritize? A few examples: A better check and displaying why the merge cannot happen forcing the user to unlink manually first? Resolve the merge conflict by automatically unlinking the problem agent first before merging? Adding an “are you sure” type of extra prompt that states the linked Agent issue and what will happen if merging occurs with a merge button? Or another resolution? Thank you.

This issue occurs when you are “deleting” a record that is linked to the record you are keeping so there shouldn’t be any reason for retaining the link(s).

My preferred resolution would be to add an “are you sure” type of extra prompt that states the linked Agent issue and that the records will automatically be unlinked if the Merge button is selected.

- not to work on right now, but probably something that can be addressed post-agents merge.