Needs option to not bring over all relationships
There is still a need to drop certain relationships during a merge (especially for those who end up with a duplicate parent relationship if you do not).
Comments
-
I've found through the years that it really is better to bring over all relationships and only after the merge address why the extra relationships are there and then properly fix the relationships. Were the parents the same? Then they need to be merged instead of one set of duplicates being lost during the merge. Was one set of parents wrong? During the merge you have no way to put a reason statement in as to why you are removing the child from one set of parents. It is better to delete the relationship either before or after the merge so you can fully explain why you are doing this. Are both sets of parents correct and you are accidentally merging two different people? During the merge is not the time to handle this. Far better to back up, reassess the whether the merge should be done at all.
I think this is one of the best changes in the merging process they are doing.
0 -
@bonniebishopbrooks @Gordon Collett thank you for your feedback. We will definitely be looking at this both ways :)
1 -
@bonniebishopbrooks @Gordon Collett update: a ticket has been created to look into providing better merge guidance. Although, we are wanting profile clean-up to be seperate from the merge.
0
