Reltio Connect

I'm still learning so hopefully my terminology is correct.

When I create a new cross walk using the REST API that should automatically merge to an existing Entity ID, I get a new Entity ID because the match and merge process is asynchronous.

In order to be notified of the final Entity ID we have to use the Reltio Events API.

Is the ENTITY_CREATED event before or after the match and merge process or are there no guarantees.

The ENTITIES_MERGED only triggers when there is a merge.

Can ENTITIES_MERGED ever be published before ENTITY_CREATED or is guaranteed to always be after?

The gap in the API I am confused about is how to know that a record is added and does not get merged because the match and merge process has confirmed it should remain where it is. i.e. a cross walk record is recreated and no automatic merge occurs.

Ideally, we want one message in from the source system into Reltio, and one message out for that transaction to send back. From what I can tell we might have listen for the two events and potentially send up to two messages back.

------------------------------
Vincent Tran
IMT
------------------------------

I'm still learning so hopefully my terminology is correct.

When I create a new cross walk using the REST API that should automatically merge to an existing Entity ID, I get a new Entity ID because the match and merge process is asynchronous.

In order to be notified of the final Entity ID we have to use the Reltio Events API.

Is the ENTITY_CREATED event before or after the match and merge process or are there no guarantees.

The ENTITIES_MERGED only triggers when there is a merge.

Can ENTITIES_MERGED ever be published before ENTITY_CREATED or is guaranteed to always be after?

The gap in the API I am confused about is how to know that a record is added and does not get merged because the match and merge process has confirmed it should remain where it is. i.e. a cross walk record is recreated and no automatic merge occurs.

Ideally, we want one message in from the source system into Reltio, and one message out for that transaction to send back. From what I can tell we might have listen for the two events and potentially send up to two messages back.

------------------------------
Vincent Tran
IMT
------------------------------

Hi Vincent!

Good question.  I assume you want the 'final' value because you need to refer to it later in your process.  The good news is that this is unnecessary.  If you GET and entity by the. ID before it was merged, you get back the same information as if you had the ID of the entity that it was merged into.  Is that helpful?

------------------------------
Gino Fortunato
Senior Solution Engineer
Reltio

Original Message:
Sent: 08-22-2023 12:18
From: Vincent Tran
Subject: How to wait for final Entity ID for Cross Walk?

I'm still learning so hopefully my terminology is correct.

When I create a new cross walk using the REST API that should automatically merge to an existing Entity ID, I get a new Entity ID because the match and merge process is asynchronous.

In order to be notified of the final Entity ID we have to use the Reltio Events API.

Is the ENTITY_CREATED event before or after the match and merge process or are there no guarantees.

The ENTITIES_MERGED only triggers when there is a merge.

Can ENTITIES_MERGED ever be published before ENTITY_CREATED or is guaranteed to always be after?

The gap in the API I am confused about is how to know that a record is added and does not get merged because the match and merge process has confirmed it should remain where it is. i.e. a cross walk record is recreated and no automatic merge occurs.

Ideally, we want one message in from the source system into Reltio, and one message out for that transaction to send back. From what I can tell we might have listen for the two events and potentially send up to two messages back.

------------------------------
Vincent Tran
IMT
------------------------------

I'm still learning so hopefully my terminology is correct.

When I create a new cross walk using the REST API that should automatically merge to an existing Entity ID, I get a new Entity ID because the match and merge process is asynchronous.

In order to be notified of the final Entity ID we have to use the Reltio Events API.

Is the ENTITY_CREATED event before or after the match and merge process or are there no guarantees.

The ENTITIES_MERGED only triggers when there is a merge.

Can ENTITIES_MERGED ever be published before ENTITY_CREATED or is guaranteed to always be after?

The gap in the API I am confused about is how to know that a record is added and does not get merged because the match and merge process has confirmed it should remain where it is. i.e. a cross walk record is recreated and no automatic merge occurs.

Ideally, we want one message in from the source system into Reltio, and one message out for that transaction to send back. From what I can tell we might have listen for the two events and potentially send up to two messages back.

------------------------------
Vincent Tran
IMT
------------------------------

Have you folks considered adding a basic "search before create" concept into your flow where you could essentially first check if an exact replica of the record already exists before trying to save a new one?  You could use a filter condition or even the real-time match API.  At least this way you don't have to go back to the queue to look for merges after the fact.  Not sure of your volumes and whether you're running big batch processes vs real-time transactional adds/updates.  Going this route would add to the number of tasks used but if it's really important that you know up front that a similar record already exists, then it may be worth the additional tasks to do the check.  

Regards.

------------------------------
Guy Vorster
Principal Solution Consultant

Original Message:
Sent: 08-22-2023 12:18
From: Vincent Tran
Subject: How to wait for final Entity ID for Cross Walk?

I'm still learning so hopefully my terminology is correct.

When I create a new cross walk using the REST API that should automatically merge to an existing Entity ID, I get a new Entity ID because the match and merge process is asynchronous.

In order to be notified of the final Entity ID we have to use the Reltio Events API.

Is the ENTITY_CREATED event before or after the match and merge process or are there no guarantees.

The ENTITIES_MERGED only triggers when there is a merge.

Can ENTITIES_MERGED ever be published before ENTITY_CREATED or is guaranteed to always be after?

The gap in the API I am confused about is how to know that a record is added and does not get merged because the match and merge process has confirmed it should remain where it is. i.e. a cross walk record is recreated and no automatic merge occurs.

Ideally, we want one message in from the source system into Reltio, and one message out for that transaction to send back. From what I can tell we might have listen for the two events and potentially send up to two messages back.

------------------------------
Vincent Tran
IMT
------------------------------

Search before create | Reltio

I don't believe it will work because Search Indexing is Asynchronous as well. This means you can create a new Crosswalk/Entity ID, but you cannot search for the record using attributes until X seconds later as well. 

If there was a stream of messages for the same brand new Contact (some source systems can be very chatty), for each one of those messages we need to send back the Entity ID. Doing a search before create will constantly create new records until search indexing is complete.

------------------------------
Vincent Tran
IMT

Original Message:
Sent: 08-24-2023 09:22
From: Guy Vorster
Subject: How to wait for final Entity ID for Cross Walk?

Have you folks considered adding a basic "search before create" concept into your flow where you could essentially first check if an exact replica of the record already exists before trying to save a new one?  You could use a filter condition or even the real-time match API.  At least this way you don't have to go back to the queue to look for merges after the fact.  Not sure of your volumes and whether you're running big batch processes vs real-time transactional adds/updates.  Going this route would add to the number of tasks used but if it's really important that you know up front that a similar record already exists, then it may be worth the additional tasks to do the check.  

Regards.

------------------------------
Guy Vorster
Principal Solution Consultant

Original Message:
Sent: 08-22-2023 12:18
From: Vincent Tran
Subject: How to wait for final Entity ID for Cross Walk?

I'm still learning so hopefully my terminology is correct.

When I create a new cross walk using the REST API that should automatically merge to an existing Entity ID, I get a new Entity ID because the match and merge process is asynchronous.

In order to be notified of the final Entity ID we have to use the Reltio Events API.

Is the ENTITY_CREATED event before or after the match and merge process or are there no guarantees.

The ENTITIES_MERGED only triggers when there is a merge.

Can ENTITIES_MERGED ever be published before ENTITY_CREATED or is guaranteed to always be after?

The gap in the API I am confused about is how to know that a record is added and does not get merged because the match and merge process has confirmed it should remain where it is. i.e. a cross walk record is recreated and no automatic merge occurs.

Ideally, we want one message in from the source system into Reltio, and one message out for that transaction to send back. From what I can tell we might have listen for the two events and potentially send up to two messages back.

------------------------------
Vincent Tran
IMT
------------------------------