Handling required Salesforce fields in the Field validation step

The Field validation mapping step in the ScheduleOnce setup wizard includes all universally required Salesforce fields that do not have a default value for the five standard objects in your Salesforce account: Lead, Contact, Account, Event, and Case.

These fields require a value in order to allow creation of a new record. The role of the Field validation mapping step is to ensure that the appropriate value is made available for bookings created via the integration. We recommend that you always set a default value for Universally required fields in your Salesforce organization. Once done, These fields will be removed from the Field validation mapping step of the Salesforce connector setup wizard.

When a booking is made and a default value is not available in Salesforce, ScheduleOnce will not be able to accept the booking and will detect a field validation error. To fix this, you should update the Field validation mapping of the Salesforce connector setup wizard. Note that you only need to fix the fields that create validation errors on the affected Booking page.

Important note: It is recommended that you make test bookings when you handle Salesforce Universally required fields in the Field validation mapping step to ensure that you have resolved all validation errors affecting your Booking pages. Note that you can make this test after each change you make in the Field validation mapping step. There is no need to complete the setup wizard.

The Field validation mapping step handles two types of fields: those that are supported by the integration and those that are not supported.

  • Supported Salesforce fields: In the Field validation mapping step of the Salesforce connector setup wizard, you will see all Universally required fields that require a value. This value can be satisfied by either a ScheduleOnce field, a static value, or an existing Salesforce value. This will ensure that a value is always associated with the required field when a new record is created. 
  • Non-supported Salesforce fields: In the Field validation mapping step of the Salesforce connector setup wizard, you will see all Universally required fields that are not supported by the integration. Since the integration does not support these fields, you have no choice but to make these Universally required fields non-mandatory for the affected Booking pages. If you still want these fields to be mandatory, you can set them as required on the Page layout. This will make the fields required for manual entry but not for the API. Once done, they will be removed from the Field validation mapping step of the Salesforce connector setup wizard.

Requirements

To handle supported and non-supported Salesforce universally required fields, you will need:

  • A ScheduleOnce Administrator.
  • An active connection to your Salesforce API User.
  • A Salesforce Administrator.

Handling supported Salesforce universally required fields

To handle supported Salesforce Universally required fields:

  1. In the Salesforce connector setup, go to the Field validation tab.
  2. In the Validation options column, select an option. You have three options that are relevant only for supported Salesforce field types:

    • A ScheduleOnce field: This list includes over 40 System fields and all Custom fields in your ScheduleOnce account.

      Important: ScheduleOnce fields requiring Customer input must be set as mandatory fields on the Booking form. Otherwise, these fields will automatically be added to the Booking form at the time of the booking and you will not have control over the order in which added fields are displayed to the Customer. Learn more about adding Custom fields to the Booking form

    • A Static value: This option maps a default text or date value to the Salesforce field.

    • An existing Salesforce value: This list retrieves the pick list values from your Salesforce account.

  3. In the Available fields/values column, select the relevant ScheduleOnce field, assign an existing Salesforce value, or type a static value.

    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. 

  4. Click the Save button or Save and Continue if you have completed mapping all required fields.


    Figure 1. Validation field mapping.

Handling non-supported Salesforce universally required fields

To handle non-supported Salesforce universally required fields, you need to identify which non-supported fields are blocking the integration.

  1. In the Salesforce connector setup, go to the Field validation tab.
  2. Review the list of non-supported Salesforce universally required fields and define which standard objects Users connected to Salesforce will be creating new records.
  3. Log in to Salesforce as an administrator.
  4. In your Salesforce Setup page, go to App Setup > Customize > Object > Fields.
  5. Select the non-supported Salesforce field you have identified earlier and ensure that is it not set as Required.
  6. Return to ScheduleOnce and refresh the page. The Field validation tab is now updated and the non-supported field disappeared.

    Important note: The API User must be connected to ScheduleOnce for the page to refresh correctly.

If you still want these fields to be mandatory for manual entry, you can set them as required on the Page layout. This will make the fields required for manual entry but not for the API.

  1. Go to App Setup > Customize > Object > <object> Page Layout.
  2. On the Page Layout page, next to the Layout you wish to work with, click Edit.
  3. On the Page Layout editor, double click the Custom field and mark it as Required.
  4. When you have completed your edits, click the Save button.

You have completed the Field validation of the Salesforce connector wizard.

Learn more about our integration with Salesforce:

Rate this article