Reltio Connect

  • 1.  Record Generator API

    Posted 08-03-2021 06:25
    Hi Team - 

    Hope All doing good ... i have a scenario which i am working on, though we can discuss on the same.

    i have 4 entities in my Tenant (say Entity - AAA, BBB, CCC, DDD).
    i have a common field in all the tenants (say Email Domain).

    Need to generate a Sequence ID w.r.to Email Domain which does not contribute to Crosswalk value (it is just a normal attribute).

    Below is the example of the scenario.
    Kindly share your thoughts on the same.

    Entity  AAA Entity  BBB Entity  CCC Entity  DDD
    Record 1 facebook.com Record 2 facebook.com Record 3 facebook.com Record 4 facebook.com
    Sequence ID 1 Sequence ID 1 Sequence ID 1 Sequence ID 1
    Record 5 gmail.com Record 6 facebook.com Record 7 yahoo.com Record 8 gmail.com
    Sequence ID 2 Sequence ID 1 Sequence ID  3 Sequence ID 2


    ------------------------------
    Chetan P
    Freshworks
    ------------------------------


  • 2.  RE: Record Generator API
    Best Answer

    Founding Member
    Posted 08-03-2021 10:47
    Maybe you could define your sequence IDs as a lookup code?:

    "lookupCode": "SEQUENCE_ID",

    {
    "SEQUENCE_ID": {
    "facebook.com": {
    "displayName": "1"
    },
    "gmail.com": {
    "displayName": "2"
    },
    "yahoo.com": {
    "displayName": "3"
    }
    },

    ------------------------------
    Walt Feldman
    Solutions Architect
    Tenerity
    ------------------------------



  • 3.  RE: Record Generator API

    Posted 08-03-2021 12:51
    Thanks for the response Walt.

    But i have nearly 300 k lookup values (in other words 300k Email domains) to be used.
    Will the above solution be feasible to implement.

    Thanks,

    ------------------------------
    Chetan P
    Freshworks
    ------------------------------



  • 4.  RE: Record Generator API

    Founding Member
    Posted 08-03-2021 13:15
    Hi Chetan,

    I doubt you want to define & maintain an ever changing list of ~300k email domains using lookup codes. In my experience, close to 90% of consumer emails are in one of 19 major email domains. Could you default the display name to "20" for "other", and map the "big 19" to a sequence ID from 1-19?

    1. aol.com
    2. att.net
    3. comcast.net
    4. facebook.com
    5. gmail.com
    6. gmx.com
    7. googlemail.com
    8. google.com
    9. hotmail.com
    10. hotmail.co.uk
    11. mac.com
    12. me.com
    13. mail.com
    14. msn.com
    15. live.com
    16. sbcglobal.net
    17. verizon.net
    18. yahoo.com
    19. yahoo.co.uk


    ------------------------------
    Walt Feldman
    Solutions Architect
    Tenerity
    ------------------------------



  • 5.  RE: Record Generator API

    Posted 08-03-2021 22:57
    Hi Walt, 

    Yes you are right !!! When we have a unique values or when we expect any unique values - we can proceed on the above mentioned approach (Which is good).
    But Email domain was just an example, i have few other attributes also to be taken care by the same method.

    For Example - i need to do the same with Email ID as well. It will not be unique across the entity, but i need to
       1) Generate new Sequence ID for new Email id
       2) Utilize the same Sequence ID for Existing email ID

    Note - This is just a normal attribute

    May be further more explanation looks like - 
    Any more approaches will definitely help me a lot ... 

    Thanks in Advance !!!!

    Entity  AAA Entity  BBB Entity  CCC Entity  DDD
    Record 1 abc@gmail
    .com
    Record 2 abc@gmail
    .com
    Record 3 abc@gmail
    .com
    Record 4 abc@gmail.com
    Sequence ID 1 Sequence ID 1 Sequence ID 1 Sequence ID 1
    Record 5 def@gmail
    .com
    Record 6 abc@gmail
    .com
    Record 7 xyz@yahoo
    .com
    Record 8 def@gmail.com
    Sequence ID 2 Sequence ID 1 Sequence ID  3 Sequence ID 2




    ------------------------------
    Chetan P
    Freshworks
    ------------------------------



  • 6.  RE: Record Generator API

    Founding Member
    Posted 08-04-2021 10:23
    Hi Chetan,

    What do you mean by "Email ID will not be unique across the entity"? If the email ID can be used as a unique identifier, you could use auto merge or better yet, a surrogate crosswalk. You you use the Entity ID, or better yet a UUID, to serve as the "sequence ID".

    Regards,
    Walt


    ------------------------------
    Walt Feldman
    Solutions Architect
    Tenerity
    ------------------------------



  • 7.  RE: Record Generator API

    Posted 08-04-2021 10:58
    Note - Below scenario are built based on sample illustration.

    Hi Walt - 
    Sorry for confusion. I will make it clear now.

    We have three sources with below mentioned attributes (Image).
    I have also mentioned sample Match rule.

    Now the question -
    Across the sources, i need to generate Sequence ID based on Email ID value.
    Say In Record 1,2,3 in below mentioned diagram, we have Sequence ID generated.
    But when we have New records incoming i.e., while having the same Email ID in the Record 4 & 5 (as of Record 1&2), it is not creating ID's rather it is reusing the existing created ID's.

    I will not be able to use Email ID in Match rule or automatic merge. 

    Need to implement this use case.

    Feel free to ask questions for clarifications.



    ------------------------------
    Chetan P
    Freshworks
    ------------------------------



  • 8.  RE: Record Generator API

    Founding Member
    Posted 08-04-2021 11:05
    Why can't set 1 record 1 merge with set 2 record 5 and Set 2 record 2 merge with set 2 record 4? Is there a business reason for persisting duplicate data?

    ------------------------------
    Walt Feldman
    Solutions Architect
    Tenerity
    ------------------------------



  • 9.  RE: Record Generator API

    Posted 08-04-2021 12:22
    You are right Walt ..
    Merging should not be done w.r.to Email ID. i.e., Match Rule shouldn't contribute in having Email ID as one of the rule.

    Summarising
    Source 1 Vs Source 2 -  Match Rule : Based on Name
    Source 2 Vs Source 3 - Match Rule : Based on Country 
    Source 3 Vs Source 1 - Match Rule : Based on Age

    Scenario of our Example - 
    Case -
    Value of Set 1 Record 1 = Set 2 Record 5
    Value of Set 1 Record 2 = Set 2 Record 1

    In our above case only the SequenceID must have impact due to above case condition (i.e., SequenceID Value).


    Match Rule can get differed but Email ID shouldn't be included. This is Business rule.

    ------------------------------
    Chetan P
    Freshworks
    ------------------------------



  • 10.  RE: Record Generator API

    Founding Member
    Posted 08-04-2021 14:48
    Have you considered making the email address a referenced attribute? Each email address could be assigned a unique sequence ID, or you could just use the entity ID of the email address. Many entities could share the same email address in this way.

    ------------------------------
    Walt Feldman
    Solutions Architect
    Tenerity
    ------------------------------



  • 11.  RE: Record Generator API

    Posted 08-05-2021 03:02
    That's Great Walt..

    I will check and try to implement the same and update in-case of any.
    This was helpful.

    ------------------------------
    Chetan P
    Freshworks
    ------------------------------