Reltio Connect

 View Only
  • 1.  Confirmation on Reltio SQS Event Messages

    Founding Member
    Posted 11-09-2023 13:41

    Hi,

    We are planning to use Reltio's SQS message functionality to stream changes that happen in Reltio. As part of that implementation, we understand that Reltio SQS queue can be configured to have Payload type as 'Delta'. Can you help answering the following 2 questions for the approach using 'Delta' payload type-

    1. For a nested attribute, if only one of the sub-attribute in the nest has been updated, can Reltio provide the entire nested attribute data in the payload or just the single attribute that was updated.
    For e.g., In our tenant we have an attribute Engagement which is a nested attribute with sub attributes, Service Area, Country and Expiration Date. So, if the expiration date of the engagement changes but all other sub-attributes are same, in the payload of the SQS message, will we only the expiration date with updated value and other attributes - Service Area and Country will not be sent?

    2. If we are using 'Delta' payload, the output of that payload only contains Reltio URIs of the entity that is being updated. Can 'Delta' payload also support sending the 'Autogenerated IDs in an entity' generated using sequence generator of Reltio.

    Thanks,
    Nikhil



    ------------------------------
    Nikhil
    ------------------------------


  • 2.  RE: Confirmation on Reltio SQS Event Messages

    Reltio Employee
    Posted 30 days ago

    Nikhil, Not sure if you got your answer to your question, but look below. Let me know if this is helpful

    For the first question,

    You can configure the Payload type as 'Delta'. The 'Delta' payload supports sending the 'Autogenerated IDs in an entity' generated using the sequence generator of Reltio.

    To configure the Payload type as 'Delta':

    1. In the Reltio console, navigate to Settings > Messaging.
    2. Click the SQS tab.
    3. In the Payload type field, select Delta.
    4. Click Save.

    Check this documentation out: External queues overview

    2nd Question:

    Reltio can provide the entire nested attribute data in the payload even if only one of the sub-attributes in the nest has been updated. This is because Reltio tracks all changes to data, including changes to nested attributes. When a nested attribute is updated, Reltio creates a change record that includes the entire nested attribute data. This ensures that downstream systems always have the most up-to-date data.

    In your specific case, if only one of the sub-attributes in a nested attribute is updated, Reltio will create a change record that includes the entire nested attribute data. This change record will be sent to downstream systems, which will then update their own data accordingly.

    Here are the steps on how to do this in Reltio:

    1. Create a nested attribute.
    2. Update one of the sub-attributes in the nested attribute.
    3. Reltio will create a change record that includes the entire nested attribute data.
    4. The change record will be sent to downstream systems.
    5. Downstream systems will update their own data accordingly.

    Documentation Here: Nested Attributes



    ------------------------------
    Chris Detzel
    Director of Customer Community and Engagement
    Reltio
    ------------------------------