Mapping ScheduleOnce fields to non-mandatory Salesforce fields
The Salesforce setup wizard includes 5 phases: API connection, Installation, Field validation, Field mapping, and Creation rules. The Field mapping step includes a default mapping and the option to map any ScheduleOnce fields to non-mandatory Salesforce fields.
In this article, you will learn how to map ScheduleOnce fields to non-mandatory Salesforce fields.
To map non-mandatory fields, you will need:
- A ScheduleOnce administrator.
- An active connection to your Salesforce API User.
Some ScheduleOnce fields are mapped to non-mandatory Salesforce fields by default. We do recommend to keep the mapping as is and not to remove mapped data from the integration. This will enable you to gather the basic customer and booking data in Salesforce.
Other ScheduleOnce fields can be mapped to additional non-mandatory Salesforce fields. You can remove them from the mapping by unchecking each field.
Important: The default mapping includes mapping for all objects supported by the Salesforce integration: Lead, Contact, Event, Account, and Cases. However, not all fields will always be in use. This depends on your booking activity and the booking pages used.
Adding new ScheduleOnce fields
You can add many ScheduleOnce fields and map them to non-mandatory Salesforce fields. This allows you to map data tracked in ScheduleOnce to Lead, Contact, Case, Account, or Event records.
Note: You cannot map ScheduleOnce fields to Salesforce universally required Custom fields. You must map required fields in the Validation field mapping.
To add a ScheduleOnce field and map to a Salesforce Field:
- In the Salesforce connector setup, go to the Field Mapping tab.
At the bottom left of the table, click the Add ScheduleOnce fields button. The ScheduleOnce field list includes System fields and Custom fields organized by categories.
Important: ScheduleOnce fields requiring Customer input must be added to the Booking form. Otherwise, the field will be automatically added to the Booking form at the time of the booking and you will not have control over its location in the form. Learn more about adding Custom fields to the Booking form
On the Add ScheduleOnce fields popup, you can see the list of ScheduleOnce fields and corresponding field types that can be mapped to Salesforce field types.
You can check the box next to each field you would like to add and click the Add fields button.
The Salesforce fields include all the fields stored in Salesforce (Custom and standard fields) that are supported by the mapping for the selected ScheduleOnce field. Learn more about the supported and non-supported Salesforce field types.
Note: There is a two-way mapping between Salesforce and ScheduleOnce. For this reason, you can only map one ScheduleOnce field to one Salesforce field.
-> ScheduleOnce to Salesforce
When a booking is made, all data is mapped from ScheduleOnce to Salesforce.
<- Salesforce to ScheduleOnce
When scheduling with existing Salesforce records using Personalized links (Salesforce ID), Customer data is mapped from Salesforce to ScheduleOnce in order to prepopulate or skip the Booking form.
- Click the Save button or Save and Continue if you have completed mapping all fields.
Deleting a mapped field
In the ScheduleOnce fields list, click the red button next to the added field you wish to delete.
In the delete verification popup, click Yes.
Click the Save button or Save and Continue.
Congratulations! You’re done.
Learn more about our integration with Salesforce:
- Connect to Salesforce as a ScheduleOnce User
- Configure the Salesforce connector settings
- Scheduling with your existing Salesforce records
- Connect an API User
- Connect ScheduleOnce to your Salesforce sandbox environment
- Install the ScheduleOnce connector for Salesforce
- Add custom fields to the Activity Event layout
- Assign the ScheduleOnce permission set to the API User
- Map ScheduleOnce fields to universally required Salesforce fields
- Salesforce record creation, update and assignment rules
- Supported and non-supported field types in the Salesforce integration
- Troubleshooting Salesforce connector issues
Rate this article