Consider the following rules and guidelines for Salesforce targets:
The source must provide non-null values for required fields in a Salesforce target object.
When you use related objects in field mappings, you need to specify the External ID for each related object.
A task might lose the least significant portion of numerical data in a Salesforce target field when the data uses most of the maximum precision and scale specified for the data type of the field.
For example, when you try to insert 65656565656565.6969 into a Salesforce field with data type Decimal (14, 4), the task inserts 65,656,565,656,565.6950 instead. When you try to insert 123456789123456789 into a Salesforce field with data type Decimal (18, 0), the task inserts 123,456,789,123,456,784.
A task might round data unexpectedly into a Salesforce target field when the data uses most of the maximum precision and scale specified for the data type of the field.
For example, when you try to insert 555555555565.8855 into a Salesforce field with data type Decimal (18, 0), the task inserts 555555555566 instead. However, when you manually enter the data in Salesforce, Salesforce rounds the data as 555555555565. When you try to insert 12345678923456.3399 into a Salesforce field with data type Decimal (14, 4), the task inserts 12,345,678,923,456.3400 instead.
When you use an Oracle source with a Salesforce target, if the source contains fields with the Number data type, change the field type to numeric. Values for fields with the Number data type do not load correctly in Salesforce. You can change the type on the
Field Mapping
page of the
synchronization
Task wizard. Alternatively, if you have many fields with the Number data type, you can add the
ASK INFAPreview
