Loading…
Microsoft Dynamics 365 Business Central (formerly NAV) is a cloud and on-premise ERP for small and mid-sized companies, covering finance, sales, purchasing, inventory, projects, and manufacturing. Businesses integrate Business Central with Dynamics 365 Sales, Shopify, Power Platform, payroll, and other line-of-business apps so that orders and financials stay consistent across the Microsoft stack and beyond. AIONDATA builds BC integrations using the standard v2.0 REST APIs, OData web services, custom API pages written in AL, and Power Automate or Logic Apps when an iPaaS approach fits.
Ready-to-scope pairs with Dynamics 365 BC on one side.
We start with the standard REST API (v2.0) which covers customers, vendors, items, sales and purchase documents, journals, and more, authenticated through Microsoft Entra ID (Azure AD). When a standard endpoint is missing a field or table, we build custom API pages in AL and deploy them as an extension, and we can use OData web services for quick read-only exposure of pages and queries.
Yes. The API surface is very similar, though on-premise requires the web services and API endpoints to be reachable, usually through a secured gateway. We also work with older Dynamics NAV versions where the approach shifts to SOAP web services and codeunits.
Yes. AIONDATA can build a custom MCP server that wraps Business Central APIs as tools, letting an AI agent in Copilot Studio, Claude, or your own app query and, with approval rules, update BC records. It runs under a dedicated app registration with only the permissions the agent needs.
Power Automate is a good fit for simple triggers and low volumes, and we build on it when a client already standardises on the Power Platform. For high volumes, complex mapping, or error handling and retries you want to own, a custom API sync is usually more reliable and cheaper to run at scale.
Tell us the other system and what needs to flow between them. You'll get an honest scope and timeline.