Skip to main content
Solved

Master data Layer matching- MDM


Forum|alt.badge.img+1

Hello, I wanted to know that how do we implement matching options in the master layer of the MDM project.

I have used in the columns in the instance layer and then used the same in the master layer in the matching step just as used in the cdi example. and then I have used the same name in the matching step but still  nothing is  showing the UI part. Can someone help me with that.

Best answer by oliver

Hi ​@Yasharth Misra. If I understand correctly all your records are coming from the source system as instances. In this case you don’t need to populate the Master matching mapping. This is used only for the matching of Authored records (created directly on the master layer without any instance).

For the matching of the instances you need to fill Matching tab on the instance table (I can see it is done for the address entity on your screenshot). They wou will get matching component generated - address_match.comp. You need to configure matching step in this matching component and then do the same for all other entities. You can see some examples in the CDI example project.

You can find documentation for the matching step here: https://docs.ataccama.com/mdm/latest/matching-configuration/matching-step.html

Also your existing records will not be rematched automatically. If this is only development or local environment, I would suggest you to drop all the tables and reload the data again after you configure the matching correctly.

Thanks,

Oliver

View original

Forum|alt.badge.img+3
  • Ataccamer
  • April 17, 2025

Hi ​@Yasharth Misra, Can you please elaborate what exactly you mean by showing the UI part? Do you want to enable matching with authored master records or do you mean displaying matching proposals in UI?

For matching of the authored records you need to enable authoring of the records and configure mapping for the matching columns. This can be done in the model in the master entity screen as you can see below:

 

Can you maybe share a screenshot what would you like to see in UI or what would you like to achieve?

You can also find related documentation on this page: https://docs.ataccama.com/mdm/latest/mixed-style-in-mdm.html#master-matching

Thanks,

Oliver


Forum|alt.badge.img+1

Hi ​@oliver  so sorry for the late reply. Thank you for responding it was very helpful. So what I mean by the ui part is that after running the project we have to go to the localhost in the browser to see the result

 

So I have 5 sources from where the data is coming 

So if I go the the master customer

 

and in one of the records  seen there is a terminal part where duplicates can be seen which should not be the case so can you help me with the configuration of the matching step in the master layer so that this issue is resolved.

So what I have done is  I have made an instance model as follows-

and so in order to apply the master matching step I have first initialized the vales in the instance layer as follows for eg-

and then used these values in the master layer for eg as follws-

and in the master layer (silver record) of the address part I have configured as follows-

I have done it for all the entities that were there in the project.

and then used these values in the matching part but still it does not seem to be working I do not know how to configure the matching part. Please help me out in this part.

Thanks again .   


Forum|alt.badge.img+3
  • Ataccamer
  • May 19, 2025

Hi ​@Yasharth Misra. If I understand correctly all your records are coming from the source system as instances. In this case you don’t need to populate the Master matching mapping. This is used only for the matching of Authored records (created directly on the master layer without any instance).

For the matching of the instances you need to fill Matching tab on the instance table (I can see it is done for the address entity on your screenshot). They wou will get matching component generated - address_match.comp. You need to configure matching step in this matching component and then do the same for all other entities. You can see some examples in the CDI example project.

You can find documentation for the matching step here: https://docs.ataccama.com/mdm/latest/matching-configuration/matching-step.html

Also your existing records will not be rematched automatically. If this is only development or local environment, I would suggest you to drop all the tables and reload the data again after you configure the matching correctly.

Thanks,

Oliver


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings