SECTIONS
The following table shows which field type mappings are supported in a field mapping definition. Note that fields are mapped according to their SOAPType, not their DisplayType. Standard Salesforce restrictions apply.
| Map To | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Map From | Type | anytype | base64 | Boolean | Date | DateTime | Double | ID | Integer | String | Time |
| anytype |
|
||||||||||
| base64 |
|
||||||||||
| Boolean |
|
|
|||||||||
| Date |
|
|
|
||||||||
| DateTime |
|
|
|
|
|||||||
| Double |
|
|
|
||||||||
| ID |
|
|
|||||||||
| Integer |
|
|
|
||||||||
| String |
|
|
|
|
|
|
|
|
|||
| Time |
|
Notes:
- When populating a String field, the value in the source field will be copied to the target field. If the target field is shorter than the source value the mapping will fail.
- When the source field is an ID field and the target is a String, the Name from the source record (not its ID) will be copied to the target field.
- When populating a Boolean field, if the source record value = Value For True the target Boolean will be set to True unless Invert Boolean Result is enabled in which case it will be set to False. If the source record value does not equal Value For True, then the target Boolean will be set to the opposite value.
- When populating any field type other than String or Boolean, if the source field cannot be converted into the target field format, the whole update process will fail.
- When the source field is a DateTime and the target is a Date, the date is stored as GMT but is displayed in the user's Salesforce locale. If the source field is a DateTime and the target is a String, the GMT value is stored as text.
- When the source field is a Date and the target is a DateTime, the date and time is stored as midnight that day in GMT but is displayed in the user's Salesforce locale. If the source field is a Date and the target is a String, the GMT value is stored as text.