FieldproxyIntegration guide · Microsoft Dynamics 365Dynamics 365 for the business. Fieldproxy for the field. No Field Service licences.
Keep Dynamics 365 for your customers and finance, and run the field work in a system built for it. In Fieldproxy, accounts and contacts are matched on the Dataverse record ID, and cases or custom work-order records that need a visit create jobs. Status, time on site, technician notes and a link to the visit report are written back to the record. Completed jobs can create invoice records for Business Central or your finance app. The field team works in Fieldproxy's app, so it needs no Dynamics 365 Field Service licence.
Fieldproxy is AI-native field service software set up around each company's workflow: dispatch, the Android and iOS technician app, your own stages, forms and checklists, stock, service agreements and invoicing. Set up for you, live within a day, with unlimited users on one price per company.
See your Dynamics 365 cases turn into jobs
Tell us which records need a visit. We map your tables and write-backs before you commit.
Why teams connect them
Dynamics 365 holds the record. The field team needs something lighter.
Dynamics 365 is often the system for customers, service cases and finance. The field side is harder: Microsoft's own Field Service app is licensed per user and is a project to configure, and contractors or seasonal crews need seats too. So many teams end up with cases in Dynamics, dispatch in a spreadsheet, and job sheets typed back in by the office.
A field service system that replaces the field tools and talks to Dataverse gives the technicians a fast app and gives Dynamics the outcome, without adding Field Service licences.
What syncs
What moves between Dynamics 365 and Fieldproxy, and when
A typical setup. Tables and columns, including custom tables, are mapped with you at setup.
| Object | Direction | When it moves |
|---|---|---|
| Accounts and contacts | Both ways | Matched on the Dataverse record ID, so the office and the field work from one customer. |
| Cases or work-order records | Dynamics 365 → Fieldproxy | Records that need a visit, by status, type or flag, create Fieldproxy jobs with the account, contact and site. |
| Job outcome | Fieldproxy → Dynamics 365 | Status, time on site, notes and a report link are written back to the record as the job moves. |
| Invoices | Fieldproxy → Dynamics 365 | Completed jobs can create invoice records for Business Central or your finance app. |
| Assets and stock | Set up per account | Fieldproxy holds sites, assets, and warehouse and van stock. Reading or writing these in Dynamics 365 is set up per account. |
| Custom tables | Set up per account | Mapped at setup, with one owner for each column. Set up per account. |
Connection: an app registration in Microsoft Entra ID, approved by your Microsoft admin, with access to the tables you choose.
See one of your own Dynamics 365 cases run through to a completed job.
Get DemoThe workflow
From case to completed visit and invoice
For breakdowns, warranty visits, installs and inspections raised in Dynamics 365.
- 1
A record needs a visit
Service agent, or a rule
A case or work-order record reaches the status or flag you chose. Records resolved remotely stay in Dynamics 365. - 2
A job is created
Fieldproxy
Account, contact, site and description come across, with the record ID kept on the job so every update finds it. - 3
It is scheduled
Dispatcher, with the Dispatch agent
The Dispatch agent ranks technicians by skills, location, free time and van stock. The dispatcher confirms; changes are previewed and can be undone. - 4
The work is done on the phone
Technician or contractor
GPS check-in, the asset's history from its QR code, your checklist with required photos and readings, parts used, and the customer's signature. Works offline. - 5
Dynamics 365 sees the outcome
Fieldproxy to Dataverse
Status, time on site, notes and the report link are written back to the record. - 6
Finance gets the invoice
Fieldproxy to Business Central or your finance app
Billable jobs create invoice records, or an invoice goes out from Fieldproxy with a payment link.
Planned maintenance
Recurring visits that never start as a case
Preventive maintenance runs on its own schedule.
- 1
Agreements live in Fieldproxy
Visit frequency, the sites and assets covered, and the checklist for each visit type. - 2
Visits appear on schedule
Each due visit is created on the board, so nothing depends on someone remembering. - 3
Faults found become cases
When a planned visit finds a fault, whether a case is raised in Dynamics 365 is set up per account, so service sees it.
What stays where
What stays in Dynamics 365, and what moves to Fieldproxy
Dynamics 365 stays the system for customers, cases and finance. Fieldproxy owns the work in the field. The spreadsheets and field apps used for that today are replaced.
Stays in Dynamics 365
- Accounts, contacts and the customer service desk
- Sales, if you run it in Dynamics 365
- Business Central or Finance: ledger, receivables, reporting
- Power BI and anything built on Dataverse today
Moves to Fieldproxy
- Scheduling and dispatch, including contractors
- The technician app: checklists, photos, readings, signatures, offline, GPS check-in
- Sites and assets with QR codes and visit history
- Warehouse and van stock with purchase orders
- Service agreements and planned maintenance
- Quotes for extra work, invoices, payment links and Tap to Pay
- A customer portal for jobs, quotes and invoices
- Your own stages, forms and checklists, in any of 27 languages
Worked example
A chiller fault at a hospital, case to invoice
A building services contractor runs customer service in Dynamics 365 and finance in Business Central.
Demo data. The company, people and numbers are made up.
- Case: Facilities manager Ruth Adeyemi at Northgate Clinic (a fictional client) reports a chiller alarm. Service agent Ben Carter logs a case and sets it to Site visit.
- Job: Fieldproxy creates an urgent job with the account, contact, site and the case ID.
- Dispatch: The Dispatch agent suggests refrigeration engineer Hana Sato, who is twenty minutes away with the right refrigerant on her van. Ben confirms.
- On site: Hana scans the chiller's QR code, sees last quarter's service readings, replaces a failed sensor from van stock and records the new readings.
- Back in Dynamics 365: The case shows on site, then complete, with time on site, Hana's notes and the report link. Ben closes the case with Ruth.
- Invoice: The reactive callout is outside the clinic's service agreement, so an invoice record is created for Business Central with the labour and the sensor.
- Next time: The sensor is now on the chiller's history, and the next planned visit's checklist includes it.
Nobody retyped the job sheet, and Hana never needed a Dynamics 365 licence.
See it built around how your team already works.
Get DemoSetup
Connected and live within a day
Your Microsoft admin is needed for the app registration and table access. The rest is done by Fieldproxy's team.
- 1
A mapping call
Which records start field work, which tables and columns matter, what is written back, and how invoices reach finance. - 2
Register the app
Your admin registers the app in Entra ID and grants it access to the tables you choose. - 3
Map tables and columns
Standard and custom tables are mapped, each column with one owner. The trigger and the write-backs are agreed. - 4
Build the field side
Job types, checklists, forms, assets, stock locations and service agreements. Sites and assets come across with free, assisted migration. - 5
Test, then go live
Run a real case through to completion and check the record in Dynamics 365. Live within a day of the mapping call.
Fit
Who it's for, and when it isn't the right fit
A good fit if
- Dynamics 365 is your system for customers, cases or finance
- Your field team, contractors or seasonal crews need an app without extra Dynamics licences
- Visits need required checklists, photos, readings and signatures
- You run planned maintenance on sites and assets
- You want the field side live quickly rather than as a long implementation
Probably not the right fit if
- You have already rolled out Dynamics 365 Field Service and it works for you
- Policy requires every process to live inside Dataverse
- There is no Microsoft admin to register the app and grant table access
- You want an add-on on top of a field app you are keeping: Fieldproxy replaces it
The usual ways to run field work with Dynamics 365, by kind of tool.
| Approach | Fits when | What you give up |
|---|---|---|
| Dynamics 365 alone, with spreadsheets for dispatch | A few visits a week by your own staff | No technician app, no required checklists, job sheets typed back by hand. |
| Dynamics 365 Field Service | You want everything in Dataverse and have budget for the licences and the project | Per-user licences, including crews, and a longer configuration project. |
| A field service system that replaces your field tools, connected to Dataverse (Fieldproxy) | You want Dynamics 365 to stay the record and the field side running quickly | A second system for the field team. Plan the switch-off date for the old tools. |
Straight answers
Dynamics 365 and field service: questions we get asked
Does Fieldproxy integrate with Microsoft Dynamics 365?
Do we need a Dynamics 365 Field Service licence?
Does it work with Business Central?
Which Dynamics 365 records can start a job?
What is written back to Dynamics 365?
How does Fieldproxy connect to Dynamics 365?
Do customer assets and inventory sync?
Can we keep using Dynamics 365 scheduling?
Can I create jobs from Copilot, Claude or ChatGPT?
How long does it take to set up?
Related
Where to go from here
Keep Dynamics 365. Give the field team a proper app.
Tell us which records need a visit. We show it running on your own tables and job types.
Get DemoLive within a day. Free, assisted migration. Unlimited users on one price per company.