Status: Public Preview — behaviour may change.

What it does

The rentals integration links Supply Chain Management's rental management to Field Service. Equipment you rent out is held as a fleet item in finance and operations, which creates a matching serviceable asset in Field Service. Service needs raised against that kit arrive as work order requests: an intake record a Field Service user approves or rejects before any work order exists.

Key facts

• Fleet items are authored in finance and operations and synchronised to Dataverse by dual-write. Creating one sets IsAsset to true and generates the Field Service asset automatically.
• Work order requests skip dual-write. Finance and operations writes them straight into Dataverse through an IOrganizationService call, so the record lives only in Field Service. Finance users see current data by querying Field Service.
• Requests can be raised from the Fleet items page, the Fleet item Damage history page, the rental contract line, or in Field Service itself. They start as Draft and only reach Field Service reviewers once submitted.
• Approving a request creates the work order automatically. Status is then derived: any open work order keeps it Approved, all work orders completed gives Completed, all cancelled gives Cancelled. The lifecycle is forward-only.
• Fleet items are mostly read-only in Field Service. You can edit Name, Rental Agreement Status and Status Reason, but those edits don't flow back to finance and operations. Rental contracts and movement history show on the fleet item and stay owned by finance and operations.
• Prerequisites at time of writing: Field Service 8.8.151.x or later, Supply Chain Management 10.0.50 or later, rental management already configured there, and a Field Service or system administrator.
• Setup is a long, ordered chain: remove the four Dynamics 365 Asset Management solutions, install the dual-write and Field Service rentals apps in sequence, enable the feature in both products, apply five dual-write solutions, refresh the entity list, then enable dual-write maps in dependency order (reference data, then product, inventory and warehouse, then rental job sites, fleet types, manufacturers, models and fleet items). Use Finance and operations as the initial sync master.
• The optional RENTALCONTRACTLINEITEMDVENTITY virtual entity brings inventory information across if you want it.

When to use / skip

Use it when a rental business already runs rental management in Supply Chain Management and wants the yard, rental desk and field technicians looking at the same piece of equipment. The approve-before-execute step is the real value: damage found on return shouldn't automatically become a scheduled job.

Skip it if you don't run finance and operations rentals, or if you can't take a preview feature into production. It's finance-and-operations-led, so Field Service on its own gains nothing from it.

Configuration decisions

• Who reviews submitted requests, and how fast. An unreviewed queue is where rental service quietly stalls.
• Which work order types and incident types suit requests raised by non-service staff, and whether service account is mandatory for them.
• Whether you also use the Field Service and Project Operations integration. If so, set that up first.
• Whether to enable the inventory virtual entity.
• Who owns the fleet item status fields, given Field Service edits don't write back.

Gotchas

• The Asset Management solutions block installation. Existing Dynamics 365 Asset Management solutions are incompatible and must be deleted first, in the documented order. Deleting managed solutions removes their components and customisations, so check dependencies before touching an environment that has history.
• Edits to an approved request don't touch its work orders, and cancelling all the work orders doesn't change the request status on its own. Reconcile them by hand.
• A reopened work order doesn't reopen a Completed or Cancelled request, so reporting off request status can lie.
• Several dual-write maps fail for missing privileges, not missing data. Check the configuring account's roles before blaming the map.
• Missing or wrong sync-master choice on initial sync is the usual cause of a map that won't start cleanly.

Consultant notes

• Treat this as a finance and operations project with a Field Service tail. The dual-write chain is where the effort and the risk sit, and it needs someone who has done dual-write before.
• Agree the Asset Management solution removal at design stage. Discovering it during a deployment window is an unpleasant surprise for anyone already using those solutions.
• Build the request review step into the rental desk's day. If nobody owns the approval queue, you've swapped immediate work orders for slow ones.
• It's a preview with version-pinned dual-write solutions. Pin the versions you tested and recheck them before each move to a new environment.

---

Revisit when rentals reaches general availability or the dual-write solution versions change.