Mapping MDM and Salesforce.com metadata
InfoSphere® MDM is code table/reference data driven. If you attempt to insert a record with an invalid code type, the transaction fails. Use these steps to import the code type from MDM and create validation rules.
About this task
The fields in Account and Contact are mapped to MDM Code types as shown in this table.
| Salesforce.com fields | MDM code types |
|---|---|
| Account Type | CDORGTP |
| Industry | CDINDUSTRYTP |
| Billing State | CDPROVSTATETP |
| Billing Country | CDCOUNTRYTP |
Based on the customer domain implementation, these reference code types can be populated and synchronized. (You must verify that the metadata is correctly synchronized between Salesforce.com and MDM.)
The current implementation of the synchronization scenario
provides following options to synchronize the reference code types.
- Account Type and Industry are a pick list in Salesforce.com. The com.ibm.mdm.integration.sfdc\mdm\configuration_mdmae_cap.sql file
contains all the default values that Salesforce.com provides. By seeding
this to MDM, you must synchronize the two fields. Note: If your implementation requires you to use different values than what is provided in Saleforce.com, you can update the pick list and insert the same values in the MDM code tables.
- Billing State and Billing Country are free form text in Salesforce.com. To verify the validation against the MDM code type, you must create a validation rule against the lookup object in Salesforce.com. The lookup object is populated with the MDM code type.