Customizing Field Mappings
By default, Informatica Cloud maps many standard and required fields of a Salesforce object to fields defined in the plan. You can customize the maps. Each Data Assessment task contains custom fields that you can use to map additional Salesforce source fields.
You can map only one Salesforce source field to any plan field. The Data Assessment task does not process plan fields that are not mapped. You can reconfigure existing maps between fields. For example, you might store two phone numbers for each account in Salesforce. You store the main phone number for each account in the Phone field and the account contact phone number in a custom Phone2 field.
The following table shows the default mappings between Salesforce source fields and the plan fields:
Salesforce Source Field | Data Assessment Task Field |
---|
Phone | Phone |
Phone2 | <not mapped> |
To perform a quality check on the phone number in the Phone2 field, you reconfigure the maps so that the Phone2 source field maps to the Phone field in the plan. You reconfigure the maps as shown in the following table:
Salesforce Source Field | Data Assessment Task Field |
---|
Phone | <not mapped> |
Phone2 | Phone |
The Data Assessment task requires fields to be included in the field mapping because it sorts and groups records for each Salesforce object based on these fields. By default, the Data Assessment task maps the required fields. If you configure the field mappings, ensure that the field remains mapped.
The following table shows the required field for each applicable Salesforce object:
Salesforce Object | Required Field |
---|
Account | BillingPostalCode |
Contact | MailingPostalCode |
Lead | PostalCode |
Opportunity | Fiscal |