"set as child" button created a rejected merge of identical ID's -

Question

As I was creating a profile, a possible duplicate was shown - which was actually the correct person. I went to accept that profile and must have chosen the wrong button (set as child) because, although everything appeared to be OK and the original profile was intergrated into my family, afterwards I discovered there was now a Rejected Match with the same profile number for both profiles. To make matters worse, I didn't discover this problem until after I'd done another sibling. Same thing: Rejected Merge of two profiles with same ID number.

Can someone please fix this? And what is that "set as child" button supposed to be used for?

Comments

Hi Marie. I'm trying to reproduce this problem but I'm having no luck. You're sure you clicked "set as child", right?

That "set as child" link should connect two previously-unconnected profiles. That is, if you were adding a child to the parent and the child you were trying to create already exists, it should connect the profiles in one step (i.e., so you don't have to make the parent-child relationship in a separate step).

Answer 1

Hi Marie,

That's odd.

I removed the rejected matches, and will try to figure out what allowed them to be created.

Thanks,

Chris