Overview
What is Dynamics 365 Business Central: Microsoft Dynamics 365 Business Central is an ERP system for small and midsize businesses.
It covers financial management, sales and service tracking, supply chain operations, project management, and inventory control. The platform exposes a REST API (v2.0, OData v4 based) that supports full CRUD operations across core business entities like customers, vendors, sales orders, purchase orders, items, and general ledger entries.
Datagrid connects to Business Central through its OData API and pulls structured ERP data into Datagrid so AI agents can process, transform, and route that data autonomously. This integration covers one-way extraction from Business Central into Datagrid for reporting, validation, and downstream routing. It does not write transactions back into Business Central from Datagrid. The integration supports scheduled imports on a daily, weekly, or monthly basis, so datasets stay current without manual intervention. Datagrid AI agents can then flag anomalies in financial records, cross-reference vendor invoices against purchase orders, or assemble period-end reports from general ledger entries.
Key data flows include outbound extraction of companies, customers, vendors, sales orders, purchase orders, items, and general ledger entries from Business Central into Datagrid. From there, AI agents can push transformed data to downstream tools such as BI dashboards, CRM systems, or document repositories, connecting ERP data to operational action.
How to integrate MS Dynamics 365 NAV with Datagrid
This integration is for operators running finance and accounting workflows that depend on current ERP data. It pulls Business Central records into Datagrid, authenticates access, and schedules recurring imports so Datagrid's AI agents can execute downstream reporting, validation, and routing workflows.
Create the connection
Start by creating the integration and selecting the Business Central records you want Datagrid to import.
Click + Create in the top left of the Datagrid screen.
Select Connect Apps.
Search for the MS Dynamics 365 NAV integration from the list.
Enter your connection details for Business Central:
OData URL
Username
Web service access key for on-premises deployments, or OAuth 2.0 authorization for Business Central Online
Authorize Datagrid's access when prompted by Business Central.
Click Next.
Select the data objects you want to import (for example, Customers, Sales Orders, Items, Vendors, and General Ledger Entries).
Click Start First Import to begin syncing.
Use this configuration format when entering the connection details:
OData URL: https://api.businesscentral.dynamics.com/v2.0/{tenantId}/{environment}/api/v2.0/
Username: your Business Central username
Auth method: web service access key (on-premises) or OAuth 2.0 (Business Central Online)
Configure authentication
Authentication depends on whether you connect to Business Central Online or an on-premises deployment.
For Business Central Online (SaaS), Microsoft requires OAuth 2.0 via Microsoft Entra ID. On-premises deployments can still use Basic Auth with a username and web service access key.
For service-to-service (S2S) integrations without user interaction, Business Central supports the Client Credentials OAuth 2.0 flow. This requires an Azure App Registration and a corresponding app configuration within Business Central itself, so the registered app can be recognized and granted access to the correct endpoints. The scope requirements depend on the endpoint family: standard APIs and web services use API.ReadWrite.All, while automation APIs use Automation.ReadWrite.All.
Schedule recurring syncs
After the first import, configure a recurring sync so Datagrid keeps the dataset current.
Open your Business Central dataset from the left side panel.
Click the ... menu in the top right of the dataset.
Click Edit Pipeline to rename your integration if needed.
Click the Schedule button next to Import Configuration.
Set the sync frequency: daily, weekly, or monthly.
Specify the time of day for each sync.
Define downtime windows if needed, which are periods when syncs should not run.
Click Update to save.
Review sync details
The integration imports Business Central data into Datagrid in one direction. The table below summarizes the core sync settings.
Direction — One-way (Business Central → Datagrid)
Frequency — Daily, weekly, or monthly (configurable)
Data objects — Companies, Customers, Sales Orders, Items, Vendors, General Ledger Entries, Purchase Orders
API version — REST API v2.0 (OData v4)
For full setup steps and integration options, see the Datagrid MS Dynamics 365 NAV integration setup guide.
Why use MS Dynamics 365 NAV with Datagrid
Teams that need answers and action, not admin, use this integration to move ERP data into execution workflows without manual exports.
Automated financial data extraction: AI agents pull general ledger entries, aged receivables, aged payables, and trial balance data on schedule, with no manual Excel exports required.
Intelligent document processing: Datagrid AI agents extract data from vendor invoices, purchase orders, and compliance documents, then match and validate against Business Central records automatically.
Cross-platform data routing: Connect Business Central data with CRM systems, data warehouses, and analytics tools through Datagrid's 100+ integrations.
Scheduled sync with zero manual steps: Configure daily, weekly, or monthly imports that keep Datagrid datasets current with Business Central's latest transactions and master data.
Autonomous exception handling: AI agents flag data anomalies, such as mismatched purchase orders, missing posting groups, or unusual GL entries, and route exceptions for human review before they compound.
Read-only audit trail preservation: Posted documents, including sales shipments, purchase receipts, and GL entries, are immutable in Business Central's API. Datagrid respects these constraints and extracts audit data without modifying the source ledger.
What you can build with MS Dynamics 365 NAV and Datagrid
Once Business Central data lands in Datagrid, AI agents can execute reporting, matching, routing, and monitoring workflows across the rest of your stack.
The examples below show the kinds of workflows teams commonly run from this integration.
Automated month-end financial reporting pipeline: Datagrid AI agents extract general ledger entries, aged accounts receivable, aged accounts payable, and income statement data from Business Central on a schedule. Agents then transform, categorize, and assemble this data into management reports, replacing the manual Excel export cycle many SMB finance teams run at period-end. Route the output to BI tools or file storage for board review.
Vendor invoice extraction and purchase order matching: Vendor invoices arrive as PDFs or scanned documents. Datagrid AI agents extract line-item data, normalize vendor details against Business Central's vendor master, and cross-reference against existing purchase orders. Mismatches get flagged and routed for human review. Matched invoices move forward for approval, which cuts manual keying from the accounts payable workflow.
Cross-platform customer and order data sync: Teams running a separate CRM alongside Business Central need customer records, quotes, and order status to stay consistent across both systems. Datagrid AI agents pull customer and sales order data from Business Central, map fields to the CRM's data model, and detect conflicts such as simultaneous address updates, handling schema translation across systems.
Inventory and demand signal aggregation: Datagrid AI agents extract item ledger entries, sales order history, and purchase lead times from Business Central. Combined with data from e-commerce platforms or external demand signals, agents analyze patterns to identify stockout risks and generate structured purchase requisition data for proactive inventory management.
These workflows keep operators focused on review and decisions while Datagrid's AI agents handle the repetitive work between systems.
Resources and documentation
Use the references below for integration setup, authentication, API behavior, and Business Central integration details.
Datagrid MS Dynamics 365 NAV integration setup guide, including prerequisites, connection steps, and scheduling configuration
Business Central API v2.0 reference covers entity reference, endpoint patterns, and supported operations
Business Central API endpoint structure covers SaaS and on-premises URL patterns
OAuth 2.0 authentication for Business Central web services covers token flows, scope requirements, and Entra ID setup
Service-to-service authentication via automation APIs covers Client Credentials flow configuration
OData web services in Business Central covers supported query parameters, pagination, and known limitations
Business Central integration overview covers architecture patterns for connecting external systems
Datagrid connectors catalog covers the full list of available integrations
These resources cover the implementation details referenced throughout this page.
Frequently asked questions
What authentication method does Datagrid use to connect to Business Central Online?
Datagrid connects to Business Central Online using OAuth 2.0 via Microsoft Entra ID. For automated, unattended connections, the Client Credentials OAuth 2.0 flow is the recommended approach. Scope requirements depend on the API family: standard APIs and web services use API.ReadWrite.All, while automation APIs use Automation.ReadWrite.All. The app must also be configured within Business Central.
What data objects can I import from Dynamics 365 NAV into Datagrid?
The integration supports importing companies, customers, sales orders, items, vendors, general ledger entries, and purchase orders. The Business Central API v2.0 entity reference documents additional entities, including sales invoices, purchase invoices, contacts, journal lines, and financial reporting views like trial balance and aged accounts receivable.
How often can I schedule data syncs from Business Central?
Datagrid supports daily, weekly, or monthly sync schedules. You configure the frequency, time of day, and optional downtime windows directly in the dataset's Schedule settings. Details are in the Datagrid MS Dynamics 365 NAV integration documentation.
Which API version does the integration use?
The integration uses Business Central's REST API v2.0 (OData v4).
How does pagination work when pulling large datasets from Business Central?
Business Central uses server-driven paging with $skipToken continuation tokens. When a response exceeds the page size, it includes an @odata.nextLink URL pointing to the next page. Standard $skip offset-based pagination does not work correctly against large Business Central datasets. Datagrid's integration handles this pagination automatically during scheduled imports.
Similar integrations
If you run Business Central at the center of your finance stack, these related integrations often appear alongside it.
Microsoft Excel: spreadsheet reporting and ad-hoc data review alongside Business Central exports and Datagrid workflows.
Microsoft SQL Server: database storage for on-premises Business Central deployments and a common warehouse target for ERP data.
Microsoft Fabric: downstream analytics and reporting for Business Central data extracted through Datagrid.
CRM systems: downstream customer record sync, order visibility, and cross-system workflow routing.
These integrations extend the same ERP data into reporting, warehousing, and operational workflows.
Browse by category
Explore related Datagrid integrations by category.
Browse these categories to find adjacent systems that connect to the same workflows.