Microsoft Dynamics 365 Business Central is an ERP platform for managing finance, sales, purchasing, inventory, projects, and other day-to-day business operations through a standard application and API surface.
The Flowgear Microsoft Dynamics Business Central Node lets you query Business Central entity sets and create or update records from a Workflow. Use it when you want Flowgear to read operational data or push business changes into Business Central through the public API.
0.1.0.3 - Current release.
0.1.0.2 - Removed query paging controls from templates and kept continuation paging inside the Node.
0.1.0.0 - Added eager startup and lazy continuation for streamed invokes.
0.0.0.15 - Aligned the V2 connector contract and public help article.
0.0.0.1 - Initial release.
0.0.0.4 - Template changes.
0.0.0.10 - Added test cases.
0.0.0.13 - Node name correction.
| Property |
Type |
Description |
Tenant ID |
String |
The Azure Active Directory tenant ID used to issue OAuth tokens. |
Client ID |
String |
The client ID from the Azure App Registration. |
Client Secret |
Masked |
The client secret from the Azure App Registration. |
Access Token |
Masked |
OAuth access token returned after delegated authorization. |
Refresh Token |
Masked |
OAuth refresh token used to renew delegated access. |
Scopes |
String |
The OAuth scopes requested during authorization. The default is offline_access https://api.businesscentral.dynamics.com/.default. |
Environment URL |
String |
The Business Central API root URL, for example https://api.businesscentral.dynamics.com/v2.0/tenant/environment/api/v2.0. |
Default Company ID |
String |
Optional default company ID used when requests do not include CompanyId. |
- Register an application in Entra ID with the Business Central permissions required for your scenario.
- Grant admin consent for the selected permissions, or ensure the signed-in user has consented.
- In Business Central, register the same application so the environment accepts the OAuth client.
- Configure the Flowgear Connection with
Tenant ID, Client ID, Client Secret, Scopes, Environment URL, and Default Company ID if you want a default company to be applied automatically.
- Test the Connection before using the Node in a Workflow.
| Parameter |
Type |
Description |
Connection |
Connection |
The connection profile used for Business Central API calls. |
EntitySet |
String |
The Business Central entity set to query, for example customers. |
Options |
Object |
A query object with optional CompanyId, Select, Filter, and OrderBy settings. |
| Return |
Type |
Description |
Response |
Array |
The Business Central rows returned by the query. |
| Parameter |
Type |
Description |
Connection |
Connection |
The connection profile used for Business Central API calls. |
EntitySet |
String |
The Business Central entity set to create records in, for example items. |
Options |
Object |
A mutation object with an optional CompanyId. |
Items |
Array |
A stream of payload objects to create in the target entity set. |
| Return |
Type |
Description |
Response |
Array |
The provider payload returned for each created record. |
Flowgear |
Object |
Default mutation fields containing IsSuccess and Message. |
| Parameter |
Type |
Description |
Connection |
Connection |
The connection profile used for Business Central API calls. |
EntitySet |
String |
The Business Central entity set to update records in, for example items. |
Options |
Object |
A mutation object with optional CompanyId and required Id values for the target record. |
Items |
Array |
A stream of payload objects to update in the target entity set. |
| Return |
Type |
Description |
Response |
Array |
The provider payload returned for each updated record. |
Flowgear |
Object |
Default mutation fields containing IsSuccess and Message. |
- Query methods do not append default mutation fields to returned rows.
- If a query returns no matching records, the Node emits zero rows.
- If the first provider query call fails, the provider error surfaces to the Workflow instead of being converted into an empty success result.
- Query templates omit
Top. The Node determines the provider page size, ignores stale saved Top values, and follows continuation links internally.
Query retrieves its first provider page while the Node invoke is awaited. It retrieves continuation pages only as the Workflow consumes rows.Create and Update execute the first input item while the Node invoke is awaited, then process later items as the Workflow consumes results. Empty Items input emits zero rows and does not send a provider mutation.- Create and Update preserve the provider payload at the root and add Flowgear mutation metadata under
Flowgear.