Hi Coti,
Few points on Compound field and Remote keys as below:
Compound Field - A compound (Source) field is created for mapping it with destination lookup field with multiple display fields.
Remote Key - is a unique identifier of an MDM object with respect to a Remote system. Its purpose is to represent an object (eg. customer) specific to a remote system (eg.ECC) in MDM.
1. In import manager, what are the prerequisites for enabling compound field? when we will go for this? what is the use?
Pre-requisites - When destination lookup table has multiple display fields , each lookup field value is a combination of lookup field values .
When we will go for this - When the lookup field and corresponding lookup table consist of multiple display fields, an additional objective is to ensure the validity of source data values not only against the individual values of each of the display fields, but also against the value combinations represented by the display fields taken together .
What is the use - Compound Field merges converted or mapped values, so that validation can be performed at the individual field level; moreover, Automap of the compound source field can then have a 100% success rate (for value combinations that already exist in the destination field) since the components of the value combination have already been validated.
2. what is the difference b/w creating remote key in import manager & syndicator?
A well known difference as below :
Import manager - If the destination table has Key Mapping enabled in the MDM Console, then the Remote Key field gets added to every field list for the table.
Syndicator - When outputting records for a remote system that has Key Generation enabled in the MDM Console, the Syndicator creates keys for that remote system on records that donu2019t already have them.
Hope this clarifies/helps you.
Regards,
Vinay M.S
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.