Individual field values within a mapping are controlled by the Field Mappings.
Fields
Salesforce field | Required. The dropdown list is pre-populated with the available fields for the selected Salesforce object. When Lead conversion applies, Contact fields are also included. |
Form field | A unique string that Send2CRM can match against your form fields to determine the submitted value. |
Inbound Mapping | Determines how the form field will be used and copied to the Salesforce field for inbound submissions. See below for more. |
Personalize | When checked the Salesforce field value will be returned to the web browser on successful form submission. See Visitor Personalization for more. |
Weight | Determines processing order when multiple mappings exist for the same field. See below for more. |
Add Field Mapping
Click the Add Field Mapping… button to bring up the form. Complete the values required for the new field mapping, then click Save Mapping. The record is added and changes are reflected on the screen immediately.
Form field
Send2CRM Visitor fields always appear in this list, and will be populated with values from the currently identified visitor. If no visitor is available these values will not exist, and the mappings will be ignored.
The dropdown list also includes two special entries by default: Data accessor and Value. Selecting either of these displays a text field where a free-form value can be entered. When Value is selected this indicates a constant or literal value; Send2CRM will automatically parse this into JSON data ready for use.
The list above also includes some additional sample values automatically populated via form capture.
If there are other mappings for the same form identifier, mapped fields from the other mappings will also be available. The Id of the relevant objects will always be included, which allows relating multiple records to each other.
Where the first form mapping supports Lead conversion and the Lead has been converted, these values will automatically refer to the same field names on the Contact. Fields that do not exist on the Contact will have null values.
Inbound Mapping Types
(Not mapped) | Select this when a field mapping is for personalization purposes only i.e. the value in this Salesforce field will be returned to the visitor's browser. In this case a matching Form field is not required. |
Matching key | The form field value will be used to locate an existing record to update. If any Matching key value is empty then the form submission will fail. Where an existing record cannot be located and new records are allowed, the value will also be used as a default. |
Default value only | The form field value will be used to populate the Salesforce object only for new records or where the existing value is empty. |
Always copy | Any time a valid record is found the value will be copied to the Salesforce field. The pre-existing value will be overwritten. |
Add to Multi-Select Picklist | Allows adding new values to a multi-select picklist field without losing any existing values set. See Multi select Picklists. |
Append text | For text fields, the incoming form value will be appended to any existing value in the Salesforce record. |
Weight
To cater for advanced functionality, Send2CRM allows mapping the same field more than once. In these cases the Weight field can be set to a number to ensure a specific processing order.
For example, most web browsers do not submit any value for checkboxes unless checked. To work around this you could create two field mappings:
A fixed false value to be applied (i.e. the un-checked value).
The form field value, which will be applied only if present.
The Weight can be safely left blank if not required.
Edit and Delete
To edit a field mapping, click the dropbutton on the appropriate row and Edit. A similar form to the add field mapping appears.
To remove a field mapping, click the dropbutton on the appropriate row and Delete. A confirmation popup will be displayed.