Microsoft Dynamics 365 Integration for NDT Companies
Connect Atlantis ERP to Dynamics 365 Business Central, Finance and Operations, or Field Service. Customers, work orders and invoices move through the Dynamics APIs; inspection results, reports and certification evidence stay traceable in Atlantis.
Who this is for
Inspection companies that run Business Central for finance, larger groups on Dynamics 365 Finance and Operations, and asset owners whose maintenance or field teams use Dynamics 365 Field Service. In each case Dynamics is doing a general job well, and the NDT specifics (method-specific reports, certifications against a written practice, calibration of instruments and probes) need a system designed for them.
What data flows, and in which direction
| Record | Direction | Notes |
|---|---|---|
| Customer | Dynamics → Atlantis (or one agreed master) | Customer numbers shared so invoices land against the right account. |
| Work order | Dynamics → Atlantis | From Field Service or asset management, creates the NDT job with the work-order reference. |
| Inspection result and status | Atlantis → Dynamics | Posted back against the work order once the report is approved. |
| Report PDF | Atlantis → Dynamics | Attached where the Dynamics app in use supports attachments on the record. |
| Invoice | Atlantis → Business Central / F&O | Posted as a sales invoice from approved timesheets and completed jobs, or billed in Dynamics from hours Atlantis sends. |
Typical architecture
Business Central publishes REST APIs (API v2.0, OData-based) for records such as customers and sales invoices, under an endpoint per environment and company. Finance and Operations exposes data entities over OData. Field Service and other Dataverse-based apps use the Dataverse Web API. Each uses an Azure AD (Microsoft Entra ID) app registration with permissions limited to the records in scope, set up by your Microsoft administrator.
Atlantis's REST API is the other end. Which Dynamics product is involved decides which API is used, but the scope conversation is the same: which records cross, who owns each field, and what triggers the transfer.
What the Atlantis side offers
Atlantis ERP has an open REST API. The same API the offline field app uses to fetch assigned jobs and issued equipment and to submit reports is available for integration, and the records an NDT company cares about are reachable through it: jobs and team assignments, NDT reports and their status, technician certifications with their computed status (active, expiring soon, expired, revoked), equipment with calibration status and due dates, timesheets, quotations and invoices. Which objects are exposed, in which direction and to which system is agreed during implementation, because every integration is scoped to the customer's landscape rather than shipped as a fixed connector.
- No prebuilt, certified connector is claimed. The integration is built against your system's published API and Atlantis's REST API during implementation.
- Your system stays the system of record for whatever it owns today, whether that is the asset register, the general ledger or the customer master.
- Mapping is agreed in writing before anything is built: object, field, direction, trigger, and what happens when a record fails validation.
What gets configured during implementation
- Scope workshop. Which records move, in which direction, and who owns each field. Anything not agreed here is not built.
- Access on both sides. A dedicated integration user or app registration on your system with the minimum permissions for the agreed objects, and API credentials on the Atlantis side.
- Key mapping. How a record in one system is found in the other: work-order number, equipment or functional-location ID, customer number, invoice number.
- Field mapping and code lists. Status values, units, methods and result codes translated between the two systems.
- Triggers and timing. Event-driven (on approval, on posting) or scheduled, depending on what your system supports and what the business needs.
- Errors and retries. Where a failed record is logged, who is told, and how it is re-sent once fixed.
- Test in a sandbox, then a controlled go-live on a small set of records before the full flow is switched on.
Business Central, F&O or Field Service: which applies to you
- Business Central: usually finance only. Customers and invoices are the core of the integration.
- Finance and Operations: finance, projects and sometimes asset management. Work orders, projects and invoices are in scope.
- Field Service: work orders and scheduling. Atlantis takes the NDT work orders and returns results; crew dispatch for NDT technicians, with certification and calibration checks, runs in Atlantis Team Assignments.
Why integrate instead of re-keying
Every NDT company that works for large asset owners ends up typing the same facts twice: the work order number from the client's system onto the job, and the result from the report back into the client's system or into accounts. Re-keying is where report numbers get transposed, where a rejected weld is closed as accepted in someone else's system, and where invoices wait because nobody has matched the timesheet to the purchase order. An integration removes the second keystroke for the records that matter, and leaves an audit trail showing what was sent, when, and what the other system replied.
If Dynamics is part of your landscape, book an integration scoping call and tell us which Dynamics products you run. See also the integrations overview, the Team Assignments app and the Invoicing app.
Frequently asked questions
Which Dynamics 365 products can Atlantis connect to?
Business Central through its REST API v2.0, Finance and Operations through OData data entities, and Dataverse-based apps such as Field Service through the Dataverse Web API. Each is scoped separately.
How is authentication handled?
Through an app registration in Microsoft Entra ID (Azure AD) with permissions limited to the records in scope, created by your Microsoft administrator.
Can technician dispatch stay in Field Service?
It can. Many NDT companies prefer to dispatch in Atlantis because Team Assignments blocks double-booking and warns when a technician's certificate or an instrument's calibration is not valid, but that is your choice.
Is there a Dynamics AppSource connector?
No. Atlantis does not claim a marketplace or certified connector; the integration is built against the Dynamics APIs during implementation.
Is this a certified connector?
No. Atlantis does not claim a certified or marketplace connector. The integration is built during implementation against your system's published API and the Atlantis REST API, scoped to the records you need.
Who owns the integration once it is live?
That is agreed in the scope: typically Atlantis maintains the Atlantis side and the mapping, and your IT team owns credentials and permissions on your system. Changes to the mapping are handled as change requests.
Sources
- SAP Business Accelerator Hub (S/4HANA APIs)
- IBM Maximo Manage REST APIs
- NetSuite OAuth 2.0 for REST web services
- QuickBooks Online API (Intuit developer help)
- Business Central API v2.0 endpoints
Speak to an ASNT NDT Level III
Atlantis NDT provides ASNT Level III consulting, NDT training to ASNT SNT-TC-1A, inspection management software and independent report validation. Request a free consultation and we will return a tailored quote — affordable, accessible and fully customizable to your programme.