--- schema_version: "1" id: 5a4e20eeb2da962a50a2799ac7b3cc679c8744cf81d82872ad408a410229a20a title: Considerations for When Salesforce Scheduler and Field Service Are in the Same Org collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/ls_limitations_fsl_with_scheduler.md canonical_url: https://help.salesforce.com/s/articleView?id=platform.ls_limitations_fsl_with_scheduler.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 940f8517746f2bbcd195464b853646399b1d3c77037c6bae225ed7897fafed26 description: Here are some things to keep in mind when you’re using Salesforce Scheduler and Field Service in the same org. products: - Scheduler - Salesforce Platform release: "264" --- # Considerations for When Salesforce Scheduler and Field Service Are in the Same Org Here are some things to keep in mind when you’re using Salesforce Scheduler and Field Service in the same org. ### Required Editions
Available in: Lightning Experience.
Available in: Enterprise and Unlimited Editions
- Salesforce Scheduler and Field Service use a common data model. As a result, these behaviors are expected. - Salesforce Scheduler work types appear on the New Work Order page in Field Service. - Salesforce Scheduler service resources appear in Field Service and vice versa. However, you can’t schedule Salesforce Scheduler service resources in Field Service and vice versa. - Skills used in Salesforce Scheduler appear in Field Service. - Service appointments created in Salesforce Scheduler appear in search results in the Field Service dispatcher console. - Service territories created in Salesforce Scheduler appear on the service territory selection page in Field Service. You can also initiate global optimization for a Salesforce Scheduler service territory, which isn’t relevant for Field Service use cases. - Salesforce system users with CRUD access on objects can see both Salesforce Scheduler and Field Service records. - Reports and dashboards show cumulative numbers because they count both Salesforce Scheduler and Field Service records. - It’s not possible to distinguish between Salesforce Scheduler and Field Service records. Based on work types and service resources used in Salesforce Scheduler and Field Service, you must create separate data archival strategies. ![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-scheduler-264-0-0-production-enus/0530be2f-891f-4263-a0d7-96ddca56a717/images/icon_tip.png) Tip You can address some of these problems through user training and by following best practices. For example, use appropriate record-level sharing for Salesforce Scheduler and Field Service users. Use separate page layouts to ensure that Salesforce Scheduler and Field Service fields aren’t commingled. Follow different naming conventions for Salesforce Scheduler and Field Service resources such as work types, service territories, service resources, and service appointments. When creating reports and dashboards, use appropriate filters based on resources, such as work types, service resources, and service territories. - When event management is enabled in both Salesforce Scheduler and Field Service, these behaviors are expected. Therefore, we recommend that you turn off event management in Salesforce Scheduler and Field Service. - For a service appointment created in Salesforce Scheduler, duplicate events are created on the Salesforce calendar—one each by Salesforce Scheduler and Field Service. - Scheduling in Field Service stops working, with this error message: `Trying to perform a heterogeneous Save with both inserts and updates.` - When a dispatcher tries to assign a service resource to an appointment, or reschedule or cancel a service appointment, the operation fails. This failure happens because Salesforce Scheduler attempts to create, modify, or delete the corresponding Salesforce calendar event and the dispatcher doesn’t have sufficient privileges to create, modify, or delete events on behalf of the service resource. - To avoid interfering with your existing Salesforce Scheduler and Field Service implementations, don’t install Shift Management in a Salesforce org where Salesforce Scheduler or Field Service is already enabled. - To use the drop-in appointments feature in orgs where you have Field Service licenses, ensure that you: - Assign permission sets created for either Field Service Agent or Field Service Resource user roles to service resources. - Create status transitions by using **Service Appointment Life Cycle** | **SA Status** | **Status Transitions**. Here’s the list of status transitions that you need for drop-in appointments. | From | To | | --- | --- | | Checked In | Scheduled | | Checked In | Canceled | | Scheduled | In Progress | | Scheduled | Canceled | | In Progress | Completed | | In Progress | Canceled | #### See Also - [Create Field Service Permission Sets](https://help.salesforce.com/s/articleView?id=service.pfs_get_started.htm&type=5&language=en_US) - [Customize the Field Service Appointment Life Cycle](https://help.salesforce.com/s/articleView?id=service.pfs_lifecycle.htm&type=5&language=en_US) - [Considerations for Shifts](https://help.salesforce.com/s/articleView?id=platform.ls_considerations_shifts.htm&release=264.0.0&type=5 "Here are some things to keep in mind when you implement shifts.")