What Data Can SmartConnect Integrate into Dynamics 365 Business Central 

One of the most common questions I get during demos is, “What data can SmartConnect import into Microsoft Dynamics 365 Business Central?” The short answer? Nearly everything—as long as there is an API. 

This blog will break down which D365 Business Central objects are available for out-of-the-box integrations, and which may require additional configuration or development. Whether you’re looking to connect customers, invoices, or custom entities, understanding D365 Business Central’s API capabilities is key to a smooth integration. 

If you’re new to D365 Business Central APIs, I recommend starting with our Introduction to D365 Business Central APIs before diving in. Throughout this post, I’ll reference different API types to help clarify what’s possible with SmartConnect. 

Understanding Dynamics 365 Business Central Object Types 

Before we start integrating, we need to first understand the different object types in D365 Business Central that define how data is accessed. D365 Business Central uses an application layer to control access to the SQL database. When working with the REST APIs, this includes Pages, API Pages, Queries, and Codeunits. Each object type serves a specific purpose, whether it’s storing records, defining business logic, or exposing read-only data. 

SmartConnect Connection Methods 

SmartConnect can connect to Dynamics 365 Business Central through either a User Impersonation (OAuth 2.0) or Basic Authentication (On-premise deployments). Once authenticated, a single connection provides access to all companies within the D365 Business Central tenant. 

A single D365 Business Central connection can be used to import into all three API types: 

• OData v4 APIs – Ideal for non-developers to access all the fields they use. 

• Standard API v2.0 – Optimized for high-performance, simplified data access. 

• Custom APIs – Designed for extended functionality beyond the standard API set. 

This flexibility ensures you can select the best API type for your specific integration needs while maintaining a quick and simple setup. 

SmartConnect can connect to D365 Business Central through Queries, Pages, and API Pages: 

• Queries & some pages (e.g., Posted Invoices) provide read-only access. 

• Pages supporting create and update operations can be selected as integration destinations. 

By leveraging all three APIs, SmartConnect ensures customizable and efficient integration with D365 Business Central. 

Data SmartConnect Can Integrate Out of the Box 

Standard Dynamics 365 Business Central 

Most common tables and fields are available to SmartConnect without custom configuration required. 

AppSource Extensions 

Some AppSource apps include custom APIs for use in integrations, and other apps make smaller changes and can be easily accessed through the ODataV4 APIs without customization. 

Here is a list of known AppSource apps that are compatible with SmartConnect: 

Custom Per Tenant Extensions (PTEs) 

Custom D365 Business Central modifications made for a single customer will typically be available through the ODataV4 APIs without requiring custom APIs. If the page performance of the integration is a concern, or real-time data sources are required, we recommend developing a custom API page for consumption by SmartConnect. 

Developers should follow Microsoft’s Best Practices when developing pages that are intended for use by SmartConnect. 

Data SmartConnect Can Integrate with Developer Assistance 

Some D365 Business Central objects aren’t accessible through the API without custom development. These objects are typically controlled by a page element that is not accessible through the API. 

The following generic areas are not accessible to SmartConnect through the D365 Business Central APIs without custom development. 

Attachments – Images and attachments in Business Central are not natively accessible by SmartConnect. The documents can be exposed as Base64 using a page object to get around the limitation. 

Codeunits – SmartConnect cannot interact directly with Codeunits, but a developer can expose a Codeunit as a page for SmartConnect to access. Here is an example where a Page API is used by SmartConnect to execute a Codeunit to post transactions. 

What SmartConnect Cannot Integrate (Limitations) 

There are a few object types SmartConnect can’t work with. These objects don’t currently have a simple workaround. 

Matrix Pages – Any page that dynamically adds columns based on a variable such as Location, will not work in the APIs (ex. “Items by Location Matrix”). 

Bound Actions – Bound Actions allow you to execute actions on a record (ex. Ship and Invoice a Sales Order). 

Control Add-ins – A control add-in (e.g., Popdock widget) is a web component that is only available through the web interface and can’t be accessed through the APIs. 

How Can You Start Integrating with SmartConnect? 

Reach out to the eOne Team. We are happy to discuss your scenarios and help build your integration plan. Contact our team to get started.