Some Member Associations make a mistake and in case of marriage resulting in the name change, simply update the player passing the new name as a parameter. This affects the deduplication process negatively! Read further to learn how to do it properly.
There is a method in our SDK, called UpdatePerson. However, the update is not as straigtforward as it might seem. If we simply replace the old name with a new name, the deduplication mechanism will only be able to find it by the new name. It will completely "forget" about the old one.
What we want to do instead, is to tell Connect ID Service, that the person can be found under any of the names: the old and the new one.
So instead of calling: UpdatePerson('new name'…) we want to do UpdatePerson({'new name', 'old name'}…). This can be done easily using the Connect ID SDK. The full technical description can be found in chapter 3.1.5.1 Handling multiple names (local, international and maiden/birth names).