Skip to main content

Hi All,

I have a scenario where I have loaded email table with 2 slightly different email data. Now next day source team sent the corrected data which is exactly equal to first data so the 2nd data gets updated but since it is exactly same it should get merged with first data but that is not happening. For email table we dont have any match rule. We just have defined a key rule on email address basically storing unique data for same load.

First Load

id email
123 abc@gmail.com
124 abc1@gmail.com

 

2nd Load

id email
123 abc@gmail.com
124 abc@gmail.com

 

Now I have duplicate email data with 2 diff id. How can I fix this? I do not have party id in this table. Party and Email are linked using Party_Email table which is having relationship for both the entities.

Party_Email

id party_id email_id
1 100 123
2 100 124

 

Hi @fshahin , could you please provide a screenshot of your model?

If the situation you are describing is no the INSTANCE layer, I would consider it correct assuming email_id 123 & 124 are matched together into a single matching group based on your Key rule i.e. have the same master_id. After that you should be able to merge those two instances into a single Master EMAIL.

If you have a relationship entity between Party and Email in your master model (EMAL represents a Golden Entity with unique email values), you would need to propagate the email matching result into that rel entity as well. Please share the model - ideally both Instance and Master to confirm my assumption. We can take it from there.

Thanks,

Ales

Thanks @Ales for looking into this. Below are screenshots of instance and master layer. Key rule is on Email_Address for email entity.

 

 

Hi @fshahin,

MDM matches(re-matches) records if one of the following re-match conditions is true:

  1. The records is a new one
  2. One of the attributes listed in the “Rematch If Changed Columns” section has changed (https://docs.ataccama.com/mdm/latest/matching-configuration/configuring-an-advanced-matching-step.html#define-rematch-conditions)
  3. Rematch flag is set to true on the record

In your case I think you should add src_email_address to the “Rematch If Changed Columns” configuration to automatically rematch email records if email address has changed 

Reply


Community Terms of Use & ConditionsCookie settings