We are looking to import historical advisor appointment data into our SAL implementation. I know that using the UI to create an Appointment also creates two related Appointment Attendee records and two related Event records. If I am bringing the data in using an ETL tool, is it safe to assume I need to create the four related records as part of the load? Are there any trigger handlers I should turn off while the ETL is running?
Thanks!
When you load via ETL, Salesforce won’t auto-generate those related records, you’ll need to create the Appointment plus the related Attendees and Events yourself. Skyvia (or any ETL) can handle that with proper mapping. I’d also test in a sandbox first and decide if you need to disable automation to avoid duplicate logic firing.
