Reltio Connect

 View Only
Back to discussions
Expand all | Collapse all

How to avoid DUNS number based matching while clicking GET MATCH Button in Reltio UI

  • 1.  How to avoid DUNS number based matching while clicking GET MATCH Button in Reltio UI

    Posted 02-03-2022 12:31
    Hi Team,

    We came across a strange scenario

    For an entity which got loaded with some other organization DUNS number from different source system and now when the data steward wants this entity to be enriched with DNB data and clicked the GET MATCH button in Reltio UI 
    then after clicking, the entity got enriched with wrong organization information because of wrong duns number and matching record from DNB has confidence score as 10 

    Now getting a matching records based on Duns number attribute should be avoided instead it should get a matching records based on Name, address, and phone number attribute when we click the GET MATCH button in Reltio UI.....but in response it should give duns number attribute value as well from dnb



    Thanks
    Izhan

    ------------------------------
    Mohammed izhan Zafeer
    ACCENTURE
    Ambur CO
    ------------------------------


  • 2.  RE: How to avoid DUNS number based matching while clicking GET MATCH Button in Reltio UI

    Reltio Partner
    Posted 02-04-2022 13:31
    Mohammed, I completely agree. It is unfortunate that some other system placed the wrong DUNS number into the organization's record. However, as regards the matching behavior within the Reltio platform, if the organization has a DUNS number populated, then Reltio should NOT match any records from D&B to that record, even using other attributes such as Name, Address. And the reason is simple. Having a DUNS number establishes uniqueness for the record. Thus, by definition, it cannot match to any other record within the D&B population. So I think if a record contains a DUNS number already, matching against D&B through the connector, should be suppressed for that record. 

    Yes the record will continue to receive updates from D&B that are incorrect for that record, but that is different problem that needs to be remediated by a data steward by removing the D&B number and the existing D&B crosswalk from the record, then re-matching the record to the correct D&B record and establishing the correct DUNS number within the record.

    ------------------------------
    Curt Pearlman
    PwC
    Agoura Hills CA
    ------------------------------

    Original Message


Related Content