Reltio Connect

Hi Community,

We have some over-merges in the Location entity, to resolve the issue we are doing unmerge using API i.e. TenantURL/entities/<entity_id>/_unmergeAllContributors. But the issue is this after triggering API, it sets Not-a-Match Flag for all contributing entities of the given entity id.

We require that after profile correction, some entities should get merged but due to Not-a-Match flag, entities are not merging.

We have ~250k such profiles and on average each profile has 5 contributing profiles. Currently, we are using this API to remove Not-a-Match 
Tenant URL//entities/<entity_id>/_notMatch?uri=<entity_id>. 

To explain more on this sceanrio, Let say we have a profile 'ABC' consisting of 5 crosswalks A, B, C, D, E. We have run unmerge API for ABC crosswalk and now we have to run API to remove NOt-a-match-flag removal for each pair it made i.e. (A,B) (A,C) (A,D) (A,E) (B,C) (B,D) (B,E) (C,D) (C,E) (D,E). So we have to run Not-a-Match API every 10 times for 250K entities, since API calls will be huge we can't go with this approach.

Can we have any alternative easy approach for this, Do we have API to remove Flag for all entities together?
or 
Is there a way if we unmerge entities, then Not-a-Match flag don't set.

Note:- We have go throught the documenation of reset Not-a-match-flag, We can't use that approach as Datastewards do many unmerges, so we don't want to remove their Not-a-match flag
Reltio

Regards,

Ankit

.

------------------------------
Ankit Agrawal
Axtria
Gurugram
------------------------------

Hi Ankit,

You have two options:

1. Apply reset Not-a-match-flag configuration temporarily during bulk unmerge execution and then remove the configuration. Make sure that data stewards are not allowed to use the system at that time.
2. Collect all the entity IDs that participated in bulk unmerge and execute the rebuild match table job for them. This job will remove the Not-a-match-flag

Please let me know if you have any questions.

Hi Community,

We have some over-merges in the Location entity, to resolve the issue we are doing unmerge using API i.e. TenantURL/entities/<entity_id>/_unmergeAllContributors. But the issue is this after triggering API, it sets Not-a-Match Flag for all contributing entities of the given entity id.

We require that after profile correction, some entities should get merged but due to Not-a-Match flag, entities are not merging.

We have ~250k such profiles and on average each profile has 5 contributing profiles. Currently, we are using this API to remove Not-a-Match 
Tenant URL//entities/<entity_id>/_notMatch?uri=<entity_id>. 

To explain more on this sceanrio, Let say we have a profile 'ABC' consisting of 5 crosswalks A, B, C, D, E. We have run unmerge API for ABC crosswalk and now we have to run API to remove NOt-a-match-flag removal for each pair it made i.e. (A,B) (A,C) (A,D) (A,E) (B,C) (B,D) (B,E) (C,D) (C,E) (D,E). So we have to run Not-a-Match API every 10 times for 250K entities, since API calls will be huge we can't go with this approach.

Can we have any alternative easy approach for this, Do we have API to remove Flag for all entities together?
or 
Is there a way if we unmerge entities, then Not-a-Match flag don't set.

Note:- We have go throught the documenation of reset Not-a-match-flag, We can't use that approach as Datastewards do many unmerges, so we don't want to remove their Not-a-match flag
Reltio

Regards,

Ankit

.

------------------------------
Ankit Agrawal
Axtria
Gurugram
------------------------------