You are here:
Microsoft Dynamics 365 Business Central Connector
Connect to an external Microsoft Dynamics 365 Business Central account. Perform tasks like managing sales orders, items, and other business resources. Use Microsoft Dynamics 365 Business Central as a data source (trigger) or a data target (action).
Required Editions
| View supported editions. |
| This feature requires the MuleSoft for Flow: Integration add-on. Professional Edition requires the API access add-on. To purchase, contact your Salesforce account executive. |
| MuleSoft for Flow: Integration features used with Agentforce require the Foundations or Agentforce 1 edition. To purchase these editions, contact your Salesforce account executive. |
Connections
To connect to a system, whether it’s a data source or a data target, you must create a connection with that system’s required credentials. You can connect to multiple systems within a flow and reuse each connection. You can create connections in the Integrations tab or in Flow Builder.
Standard Connection
This system uses OAuth2ClientCredentials authentication.
OAuth2ClientCredentials authentication obtains an access token from a user-defined path.
This system requires this credential information for its connections.
| FIELD | DESCRIPTION |
|---|---|
| Connection Name | Enter a unique connection name that helps you remember the details of this connection. The credentials are hidden after you create the connection. You can reuse connections. Anyone with the Manage Integration Connections permission can see and use all connections in the org. |
| ClientId | Enter the OAuth client ID to use to authenticate the requests. |
| ClientSecret | Enter the OAuth client secret to use to authenticate the requests. |
| URL | Enter the URL to use to authenticate the requests. |
| Scope | Enter the scopes that the client can access. |
| Token URL | Enter the URL to use to get an access token. |
| CompanyId | Enter the company ID. |
Named Credential Connection
Select a pre-existing named credential from Setup to use for your external system connections.
Before connecting to your external system with a named credential, first create or use an existing authenticated named credential and external credential that is enabled for your users.
To ensure a successful connection for use in a flow, use only one principal for each named credential.
- Use the same name for the named credential and its related objects, such as the external credential and external authentication identity providers. Labels for these objects can differ.
- Assign the user creating the connection the required user permission for the principal. Without this permission, the connection test fails and the connection remains inactive.
When you create a connection with an existing named credential, note these behaviors:
- Manage the named credential’s read-only details in Setup, not the Integrations tab. On the Integrations tab, you can only edit the connection's Connection Name and Description.
- Perform reconnections for the named credential in Setup. The Reconnect button isn’t visible on the Details page.
- Delete associated named credentials in Setup. Deleting a connection doesn't remove the credential.
Triggers
A trigger initiates the flow when a specified event occurs. Triggers are important for automating business processes because they react to real-time data changes in various systems. For more information about triggers, refer to Create a Flow with a Connector as a Trigger.
These Microsoft Dynamics 365 Business Central triggers are available in Flow Builder.
- On New or Updated Customer
- On New or Updated Item
- On New or Updated Sales Invoice
- On New or Updated Sales Order
Actions
An action performs a specific task or operation within a target system. Use actions to automate tasks across different systems without manual intervention, based on conditions set in the flow. For more information about actions, refer to Create a Flow with a Connector as an Action.
These Microsoft Dynamics 365 Business Central actions are available in Flow Builder.
- Create Customer
- Create Item
- Create Sales Invoice
- Create Sales Invoice Line For Sales Invoice
- Create Sales Order
- Create Sales Order Line For Sales Order
- Delete Customer
- Delete Item
- Delete Sales Invoice
- Delete Sales Invoice Line For Sales Invoice
- Delete Sales Order
- Delete Sales Order Line For Sales Order
- Get Customer
- Get Records
- Get Item
- Get Sales Invoice
- Get Sales Invoice Line For Sales Invoice
- Get Sales Order
- Get Sales Order Line For Sales Order
- Patch Customer
- Patch Item
- Patch Sales Invoice
- Patch Sales Invoice Line For Sales Invoice
- Patch Sales Order
- Patch Sales Order Line For Sales Order
Get Records Action
Query searchable objects from each connector by using custom filter logic in the MuleSoft for Flow: Integration Get Records action, which functions like the Salesforce Flow's Get Records element.
The MuleSoft for Flow: Integration Get Records action:
- Defines queried object to ensure flexibility and adaptability across different data sources.
- Specifies available operators and enables the selection of fields and addition of conditions.
- Defines the logical operator types.
- Includes other metadata to describe the operators available for each field when the available operators differ based on the object type.
- Runs the query request, processes the response, and formats the retrieved data accurately.
- Limits the number of records returned to optimize performance and makes sure that you have access to the most relevant data.
For information about specific limitations for connections and third-party connectors, see MuleSoft for Flow: Integration Limits & Considerations.
