Skip to main content

I  have a full load already configured for a source system. This load component has 3 different entities(party, contact, address).I have used this to load data into mdm-hub as well.
However, now we want to use a different source table for party entity and want to load only the records for party entity. I am planning on using a new full load with mappings only for the party entity. Will this

  1. create new instance party records and make the old records inactive?
  2. bring any change to the records for contact and address entities?

 

Hi ​@aish_TF, assuming that the second full load operation is related to the same system and will contain the same SOURCE_IDs?

If so

  1. will create new records and update the existing records based on the SOURCE_IDs; and deactivate the non existing ones.
  2. the load itself will not bring any change to the child entities unless you have e.g. copy columns defined in your model and match the related addresses/contacts based on the matching on the parent-Party entity.

Hi ​@aish_TF  I’m closing this thread for now, if you have any follow-up questions please share them here or create a new post 🙋‍♀️

​@Ales  Can you explain what changes will come into affect for point 2. 
I do have copy columns in address and contact that are fetched from party. These are used to determine address and contact matches.
 

if you have copyColumns configured (copying a value from e.g. Party to Address) and there are child records related to the parent Party, the value from Party will be copied to the child which will change that way.

So only your CopyColumns attributes may change on the child entity + subsequently it may have an impact on your matching if configured on child entity.

Reply


Community Terms of Use & ConditionsCookie settings