Reltio Connect

 View Only

  • 1.  Ability to get 'Not A Match' export from Reltio

    Founding Member
    Posted 06-15-2021 10:59

    In the UI you can see when 2 profiles have been stewarded and selected as 'Not A Match'.   Is there a way to get this information out of Reltio,  to see Reltio_uri_1 not a match Reltio_uri_2?

     

    Thanks!

    Angie

     

     

    Angela Wawrzaszek
    MDM Manager 
    Master Data Management - Data standardization and process alignment 

    +1 315.291.3565 office 
    Angela.Wawrzaszek@Hillrom.com 

    Hill-Rom 

    hillrom.com 


     

     

     



    CONFIDENTIAL NOTICE: If you are not the intended recipient of this message, you are not authorized to intercept, read, print, retain, copy, forward, or disseminate this communication. This communication may contain information that is proprietary, attorney/client privileged, attorney work product, confidential or otherwise legally exempt from disclosure. If you have received this message in error, please notify the sender immediately either by phone or by return e-mail, and destroy all copies of this message, electronic, paper, or otherwise.



  • 2.  RE: Ability to get 'Not A Match' export from Reltio
    Best Answer

    Reltio Employee
    Posted 06-16-2021 11:13
    There are effectively three methods:

    1. You can subscribe to the business event POTENTIAL_MATCHES_REMOVED in the queue
    2. If you are looking for events on a specific entity you can query that entity directly.  Details on this API are available at: https://docs.reltio.com/entitiesapi/geteventsperentity.html
    3. Query the activity log.  This can be done either through the Dashboard UI or via the API.  Details on the API are available at: https://docs.reltio.com/activitylogapi/activitylogapi.html


    The specific query for option 3 is a REST GET: https://{{environment}}.reltio.com/reltio/api/{{tenantID}}/activities?filter=(equals(items.data.type,%20NOT_MATCHES_SET%20))

    In the UI it would look like this: 



    ------------------------------
    Daniel Gage
    ------------------------------

    Original Message


  • 3.  RE: Ability to get 'Not A Match' export from Reltio

    Founding Member
    Posted 06-16-2021 13:12

    Thank you Daniel,    I got the Rest API to work!

     

    Next question,  this returns Reltio URI's for the not a match pairs.  Is there a way to get Crosswalk Key returned instead?   The Reltio URI is unstable,  it may exist today and does not tomorrow and makes it hard to tie back to the true Crosswalks that were flagged as not a match. 

     

    Ie.  Last month   URI 123456 was set as not a match to URI 654321.   If I want to know what crosswalks were set as not a match I would need to look at all crosswalks under each URI.   However URI 654321 no longer exists because it was merged to URI 8888888. 

     

    Angela Wawrzaszek
    MDM Manager 
    Master Data Management - Data standardization and process alignment 

    +1 315.291.3565 office 
    Angela.Wawrzaszek@Hillrom.com 

    Hill-Rom 

    hillrom.com 


     

     

     



    CONFIDENTIAL NOTICE: If you are not the intended recipient of this message, you are not authorized to intercept, read, print, retain, copy, forward, or disseminate this communication. This communication may contain information that is proprietary, attorney/client privileged, attorney work product, confidential or otherwise legally exempt from disclosure. If you have received this message in error, please notify the sender immediately either by phone or by return e-mail, and destroy all copies of this message, electronic, paper, or otherwise.




    Original Message


  • 4.  RE: Ability to get 'Not A Match' export from Reltio

    Reltio Employee
    Posted 06-16-2021 14:06
    URI (Reltio entity ID) are technically never lost.  

    If URI 654321 is merged to URI 8888888 the policy is that the oldest URI will be preserved as the primary URI for the new consolidated record, but a GET on either URI will return the same consolidated record.  Consumed / non-primary URI will be returned in a GET as "loserUri".  

    The potential challenge lies in a not-a-match event being triggered on the consolidated 654321/8888888 record.  But in this case, it should be inferred that if 123456 is indicated as not-a-match to the consolidated 654321/8888888 record that it is equivalent to flagging 123456 as not-a-match to 654321 and 8888888 each (and their corresponding source crowwalks).  

    ------------------------------
    Dan Gage
    Principal Solution Consultant
    ------------------------------

    Original Message


  • 5.  RE: Ability to get 'Not A Match' export from Reltio

    Founding Member
    Posted 07-22-2021 08:41

    Hi Dan,

     

    My technical is beginning to look at this and hoping you can answer a QQ.   The methods below appear to give full history of all not a match.   What I am hoping to pull is what are the current profiles in Not a Match status right now. 

     

    Ie. 

    URI 1 and URI 2 – set to Not a match   7/21/2021

    URI 3 and URI 4 -  set to Not a match   7/21/2021

     

    Data Stewared determines URI 1 and URI 2 are a match and merges them.

     

    On 7/22 – pull report to find all Not a Match Records.     Only URI 3 and URI should show on the report. 

     

    We will not be pulling this by a specific entity but rather pull ALL not a match pairings as of the time the extract is taken.

     

    Do you know if this is possible?

     

    Thank you for your support!

    Angie

     




    Original Message


  • 6.  RE: Ability to get 'Not A Match' export from Reltio

    Reltio Employee
    Posted 07-23-2021 10:16
    I don't think we can do this in a single pull.  Having records flagged as not-a-match is metadata which is stored, but does not appear to be directly accessible in an API which searches across multiple records.  Specifically we just return the records which are flagged as not-a-match for a specifically requested record.

    I think the most certain way to get your desired result might be to extract all the not-a-match events from the activity log then have a second pass process which validated which of those records meet your desired condition.  There is an event for "not-a-match reset", so you may get those records and remove them from the original set, but i'm not sure there is an assurance that the not-a-match references would be on the same pair of records.

    ------------------------------
    Dan Gage
    Principal Solution Consultant
    ------------------------------

    Original Message