Dynamics Community Forum Thread Details

Power Platform solution working with/without Field Service (Work Order dependency)

Hi all,

I’m working on a Dynamics 365 Field Service / Power Platform solution and would appreciate some architectural guidance.

We currently rely on Field Service entities such as Work Order (msdyn_workorder), Work Order Type, and Incident Type to drive scheduling and booking logic.

However, we now have a requirement to support customers who do NOT have a Field Service license, while still allowing customers who DO have Field Service to use Work Orders and related functionality.

Our goal is to package the solution as a managed solution that:

Works out of the box in environments without Field Service
Also integrates with Work Orders when Field Service is available

Our current idea is:

Move all scheduling logic to Resource Requirement (msdyn_resourcerequirement)
Introduce a custom “Call Type” table to replace Work Order Type / Incident Type
Store Call Type on Requirement and use it to drive duration and scheduling
Keep Work Order only as an optional UI layer for Field Service users
Sync Work Order → Requirement (one way) when FS is present

Key questions:

Is it technically possible to include Work Order customizations (custom button/dialog etc) in a managed solution that should also install in environments without Field Service?
Is splitting the solution into:
- Core (no FS dependencies)
- Field Service extension (Work Order logic)
  the only safe approach?
Has anyone successfully implemented a "URS-only" scheduling model (Requirement → Booking) while optionally supporting Work Orders?
What are the common pitfalls when decoupling from Incident Type and Work Order Type?