Data Load Considerations for Importing Sessions and Bookings
If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.
Table of Contents
This article covers the records and other fields that are involved in migrating Sessions and Bookings.
What are the objects involved?
This depends on the data that you plan to migrate.
If you plan to migrate the session and let RIO Education to generate the session's bookings, you need to load the data into:
After migrating the data, you need to update the Session's Booking Status = Create/Update Bookings to have RIO Education to generate the Session's bookings.
If you plan to migrate the session together with the scheduling data from your legacy system, you need to load the data into:
- Session Time.
What are the important fields?
|Name||The name for the Session.|
|Booking Status||Default to "Draft". If you plan to migrate scheduling data, set this to "Booked".|
|Capacity||The maximum capacity for the Session.|
|Course Offering||The course offering for the Session.|
|Plan Line||This will be auto generated.|
|Published||To allow external users to see the Sessions e.g., calendar.|
|Record Type Id||Default to "Class" record type.|
|Session Type||The Session type e.g., lecture.|
See also: Session
|Day of Week||The day of week e.g., Monday.|
|End Date||The last day of the Session Time.|
|End Time||The end time of the Session Time.|
|Label||The label or name for the Session Time.|
|Recurrence||The recurrence of the Session Time e.g., Weekly.|
|Session||The session for the Session Time.|
|Status||Default to "Active".|
|Start Date||The first day of the Session Time.|
|Start Time||The start time of the Session Time.|
|Create/Update Settings||Default to "Create/Update from today". If plan to generate all bookings including the past, set to "Create/Update All".|
|Historical Recurrence||Default to the same value as "Recurrence" field. This is to avoid the recreation of Session's booking when user updated the Session after migration.|
See also: Session Time
|Booking Status||Default to "Tentative".|
|Display Name||The name for the parent Session.|
|End||The end date/time for the Session on a particular day.|
|End Date (Non TZ)||The end date for the Session on a particular day following the campus timezone.|
|End Time (Non TZ)||The end time for the Session on a particular day following the campus timezone.|
|Plan Line||The Plan Line record for the parent Session.|
|Resource||Optional. The resource for a Facility record.|
|Start||The start date/time for the Session on a particular day.|
|Start Date (Non TZ)||The start date for the Session on a particular day following the campus timezone.|
|State Time (Non TZ)||The start time for the Session on a particular day following the campus timezone.|
|Session Time Id||The Salesforce 18 characters id for the related Session Time that this booking belongs to.|
See also: Plan Lines and Bookings
What datetime format and timezone should be used?
The datetime field in Salesforce is timezone sensitive. When migrating date, you should review the datetime value that you have from the legacy system and define the correct timezone settings in the data loader.
Salesforce shares the same datetime format as the one supported in SOAP API and BULK API. Please also review the common mistake when loading date and datetime field in Salesforce.