Field Service Settings

What it does

Field Service Settings is a single configuration record (msdyn_fieldservicesetting) that holds the app-wide defaults: whether pricing and costing are calculated, how agreements generate work orders and invoices, which optional features are switched on, and how records are numbered. Almost every "why does Field Service do that?" question on a project ends up here.

Key facts

One record per environment, reached from the Settings area of the Field Service app under General > Field Service Settings. There is no supported multi-record or per-business-unit variant.
Tabs, as shipped: Features, Work Order / Booking, Agreement, Purchase, Intelligence, Field Service SLA Configuration, Time Entry, Mixed Reality, Inspection, and Other. Each tab is saved separately — changing values across two tabs and hitting Save once is a common way to lose half your edits.
The Features tab is the feature switchboard, and everything on it is off by default: Enhanced characteristics (in a Preview section), Copilot for work order, Copilot in Microsoft Outlook, Insurance policies, Trades, Warranties, and Not-to-Exceed. Nothing appears in the navigation until the relevant toggle is on.
Calculate Price and Calculate Cost on the Work Order / Booking tab control whether pricing and costing fields and logic exist at all. Setting Calculate Price to No strips the pricing fields and disables invoice generation outright.
Work Order Invoice Creation decides whether an invoice is generated automatically when a work order reaches Closed - Posted. Default work order completed status picks Completed or Posted as the end state.
Default Warehouse is only applied when a warehouse is required and the field is blank on the work order product. It does not stamp every line, and it never overwrites a warehouse someone has already chosen.
Agreement generation is driven from the Agreement tab: Auto Generate Work Order for Agreement Booking, Generate Booking Dates X Months in Advance, Generate Invoice Dates X Months in Advance, Generate Agreement Work Order X Days in Advance, Generate Agreement Invoices X Days in Advance, and Record Generation Timing, which runs against the agreement owner's time zone rather than the organisation's.
Auto-numbering is opted into from the command bar (Opt-In to Auto-Numbering, then Auto-Numbering for entity, prefix, number length and starting number). The dialog only handles simple formats such as WO-{SEQNUM:6}; anything with placeholders after the sequence number has to be set on the column in Power Apps.
Use Enhanced Background Processing on the Other tab is explicitly labelled Preview. It swaps the classic workflows that drive agreement background jobs for Power Automate flows, and Microsoft's own text says it is less stable than workflows and may still change in design.

When to use / skip

This isn't optional. Every Field Service implementation touches this record in the first week, and getting it wrong is expensive later. What you can skip is the temptation to turn everything on during discovery: Warranties, Trades, Insurance and Not-to-Exceed each bring their own tables, forms and data-entry burden, and a client who asked for "warranty tracking" in a workshop often means a text field on the asset. Turn on what phase one genuinely needs and leave the rest, because switching a feature on mid-project is easy and unpicking the data people entered against it is not.

The costing settings deserve real thought rather than acceptance of the defaults. Organisations that bill from an ERP and only use Field Service for execution are usually better served by turning pricing and costing off — but that decision has to be made with the finance workstream, not by an admin clicking through tabs.

Configuration decisions

Whether work orders carry price, cost, tax and invoices at all, or whether billing lives in a finance system and Field Service just records what happened.
Which end state a completed job lands in — Completed or Posted — and how that lines up with the invoicing and actuals process.
Whether agreements generate their work orders and invoices automatically, how far ahead, and at what time of day that generation runs given owner time zones and a possibly global user base.
Which of the Features toggles are in scope for phase one, and who owns the data model that each one drags in.
Whether to adopt auto-numbering, in what format, and whether the format is simple enough for the built-in dialog or needs configuring on the column in Power Apps.
Whether to run background agreement processing on classic workflows or the preview Power Automate flows path.

Gotchas

Opting in to auto-numbering while people are working can cause record creation to fail during the initial opt-in. Do it in a quiet window, and do it before anyone has a numbering expectation baked into a report.
Each tab saves independently. "My change didn't apply" is nearly always a Save on the wrong tab.
Turning Calculate Price off to hide pricing from users is the classic mistake — it also kills invoicing. Hide the fields on the form instead.
Settings appearing read-only or absent usually means the user lacks the Field Service - Administrator role.
The Mixed Reality tab still offers automatic assignment of Guides and Remote Assist security roles, but both products are announced as unavailable after 31 December 2026. Don't build a rollout on it.
Address geocoding silently does nothing if Auto Geo Code Addresses on the Other tab is off, and travel-time scheduling degrades without any obvious error.

Consultant notes

Screenshot or export the settings record at the end of each environment build. There's no solution-aware way to move this configuration, so someone will be re-keying it into production and you want a checklist.
Demo the Features tab early with the client's process owner in the room. It's the fastest way to have the "do you actually need warranties in phase one?" conversation with something concrete on screen.
Push back on requests to switch pricing off purely for tidiness. Ask what the invoice source of truth is, then decide.
Before go-live, confirm the agreement generation window and timing against the client's real support calendar — nobody wants a year of maintenance work orders appearing at 10am on a Monday.
If Copilot in Outlook is on the table, flag the data-processing statement: enabling it accepts that data may be processed outside the tenant's geographic or compliance boundary. Some clients will stop the conversation there.

Worth another look after each April and October release, since the Features tab is where new capability quietly shows up first.