Integrate iPaaS.com with Microsoft Dynamics 365 Business Central to synchronize customers, companies, contacts, customer categories, products and inventory, product categories, locations, shipping methods, sales orders, and posted invoices between the two systems.
This article is the ongoing connection reference for the integration. It describes what each credential and setting does, how authentication works, and how to maintain the connection after the initial setup, for example when rotating credentials or changing environments. For the first-time setup walkthrough, subscribers or their MiSP should follow the Installation Instructions.
How to Connect
Prerequisites
Before setting up the Microsoft Dynamics 365 Business Central integration in iPaaS.com, ensure you have the following:
A Microsoft Dynamics 365 Business Central account with administrator access.
Access to the Microsoft Entra Admin Center to register an application.
The following values from the registered application:
Tenant Id
Client Id
Client Secret
Scope
How to Create an Application for the iPaaS.com Integration
To set up authentication, an application must be created in the Microsoft Entra Admin Center. Follow these steps:
Navigate to the Microsoft Entra Admin Center.
Log in with your Microsoft administrator account.
Go to Applications → App Registrations.
Click New Registration.
Provide a display name for the application.
Select the appropriate option to determine who can use the application.
Provide a Redirect URI (optional). Use the following URI for returning authentication responses: https://portal.ipaas.com/customer/subscription-mgmt/subscriptions/authorization/app
Steps to Generate Client Credentials
Open the Certificates & Secrets tab.
Click New Client Secret.
Add a description and set the expiration period for the client secret.
Click Add to generate the client secret. Copy and store the value securely, as it is shown only once.
Steps to Add Permissions for Business Central
To grant the permissions the integration needs:
Navigate to API Permissions for your application and click Add a Permission.
In the Request API Permissions dialog, select Dynamics 365 Business Central. This grants access to Business Central data and functionality.
Assign the desired Application Permissions to the application. For example, select an application permission such as the read/write permission for full API access.
Review the permissions added under API Permissions, and verify that all required permissions are present and correctly assigned.
Enable Web Services in Business Central
The integration reads from several Business Central web services. In Business Central, search for Web Services, then add and publish each of the services below:
Search for Web Services and open the page.
Select New to add a web service.
Choose the appropriate Object Type and Object ID.
Enter the Service Name.
Select Publish.
Repeat for each service in the table below.
Name | Object Type | Object ID | Service Name |
Customer Card | Page | 21 | CustomerCard |
Location Card | Page | 5703 | Locations |
Item Card | Page | 30 | ItemCard |
Shipping Agents | Page | 428 | ShippingAgents |
Sales Order | Page | 42 | SalesOrders |
Sales Order Lines | Page | 46 | SalesOrderLines |
Items By Location | Query | 2554 | Itemsbylocation |
Customer Price Groups | Page | 7 | CustomerPriceGroups |
Configure Subscription Settings
The fields below configure your Microsoft Dynamics 365 Business Central subscription in iPaaS.com. The first group establishes the connection and authentication; the second group tunes optional integration behavior. Subscribers or their MiSP enter these values on the subscription settings page.
Connection and Authentication Settings
Field | Description | Required | Example |
API Url | The base API address for Microsoft Dynamics 365 Business Central. | Yes | |
Environment | The Business Central environment that the integration connects to, such as a sandbox or production environment. | Yes | Production |
Company Name | The name of your company in Business Central. Requests are scoped to this company, so it must match the company that holds the records you want to synchronize. | Yes | YourCompany |
Tenant Id | The directory (tenant) Id from the application registration. | Yes | Your tenant Id |
Client Id | The application (client) Id from the application registration. | Yes | Your client Id |
Client Secret | The secret value generated for the application. Store it securely, as it is shown only once. | Yes | Your client secret |
Scope | The permission scope requested for the Business Central API. | Yes | |
Grant Type | The OAuth 2.0 grant the integration uses to obtain a token. Must be set to client_credentials. | Yes | client_credentials |
The subscription also has a Name that identifies it within iPaaS.com (for example, Dynamics365_Integration). This is the general subscription label and is not a Business Central credential.
Optional Behavior Settings
These settings adjust how specific data flows behave. Each one is optional; when left blank, the integration applies the default shown.
Field | Description | Required | Default |
Transaction Poll Search Days | How many days back the scheduled sales order poll looks for recently modified orders, invoices, and shipments. Increase it to widen the lookback window. | No | 5 days |
Concurrent Batch Executions | How many requests the integration runs at the same time when processing data in batches. Lower it to reduce load on the Business Central API; raise it to process larger volumes faster. | No | 10 |
Enable Company Hierarchy (TRUE/FALSE) | When set to TRUE, the integration includes parent and child company relationships when transferring companies to iPaaS.com. | No | FALSE (off) |
PROCESS COMPANY RELATIONSHIP (TRUE/FALSE) | When set to TRUE, the integration includes contact relationships when transferring companies to iPaaS.com. | No | FALSE (off) |
Contacts Endpoint | The Business Central endpoint used to read contact records for company relationships. Leave blank to use the standard contacts endpoint; set it only if your environment exposes contacts under a different web service name. | No | contacts |
Transfer Customer Price Groups | When set to TRUE, the integration transfers customer price group pricing along with products. | No | FALSE (off) |
Sales Codes For Customer Price Groups | The sales codes used when transferring customer price group pricing. Applies only when Transfer Customer Price Groups is enabled. | No | None |
Sales Price Field Separator | The character that separates fields within a customer price group price record. Applies only when Transfer Customer Price Groups is enabled. | No | None |
Sales Price Record Delimiter | The character that separates one customer price group price record from the next. Applies only when Transfer Customer Price Groups is enabled. | No | None |
Exclude Expired Rules | When set, the integration omits expired customer price group pricing rules. Applies only when Transfer Customer Price Groups is enabled. | No | None |
EXCLUDED LINEITEM SKUs FROM PREPROCESSING | A list of SKUs to skip during sales order line preprocessing. Leave blank to process all line items. | No | None |
Processing Company Creation In Prerequisite | When set to TRUE, allows a missing company to be created as a prerequisite during transfer rather than causing the transfer to wait. | No | FALSE (off) |
Update Non-Existing Invoice Lines | When set to TRUE, the integration adds invoice lines that are present in the iPaaS.com record but not yet on the Business Central invoice when posting invoices from iPaaS.com. | No | FALSE (off) |
How to Populate the Connection Settings
Follow these instructions to locate each value and populate the subscription fields in iPaaS.com:
API Url: The base API address for Microsoft Dynamics 365 Business Central is https://api.businesscentral.dynamics.com.
Environment: The environment (for example, a sandbox or production environment) is configured in Business Central. To locate it, go to Settings → Admin Center in Business Central.
Navigate to Operations to view and select the environment.
Grant Type: Must be set to client_credentials in all configurations.
Client Id:
Log in to the Microsoft Entra Admin Center.
Go to App Registrations.
Locate the application you registered and copy the Application (client) Id.
Client Secret: Generate a client secret in the Microsoft Entra Admin Center:
Open your application in App Registrations.
Click Certificates & Secrets.
Create a New Client Secret. Save it securely, as it is shown only once.
Scope: Set to https://api.businesscentral.dynamics.com/.default. The scope value is the resource identifier of the resource being requested, suffixed with .default, which requests the resource service generically without naming individual permissions.
Tenant Id:
Navigate to App Registrations in the Microsoft Entra Admin Center.
Copy the Tenant Id from the Overview page.
Company Name: The name of your company in Business Central is required. To locate it, go to Settings → My Settings in Business Central and check the Company Name field.
External and Internal IDs
When transferring data between Microsoft Dynamics 365 Business Central and iPaaS.com, External IDs and Internal IDs identify each record so updates land on the right record rather than creating duplicates.
Transferring Data from Microsoft Dynamics 365 Business Central to iPaaS.com
To transfer data from Microsoft Dynamics 365 Business Central to iPaaS.com, you need the External ID of the Business Central record. The following data types are supported:
Company and Customer
Sales Order
Product
Location
Shipping Method
Company and Customer
Navigate to Microsoft Dynamics 365 Business Central → Sales → Customers.
Open the customer you want to transfer.
Use the Customer No as the External ID.
If the customer type is Company, it is added as a company in iPaaS.com.
If the customer type is Person, it is added as a customer in iPaaS.com.
In iPaaS.com, open a manual submission via Integration Monitoring → Manual Sync and complete the fields:
Field | Data |
System | Microsoft Dynamics 365 Business Central |
Mapping Collection | Dynamics Company Add/Update to iPaaS |
Scopes | Created/Updated |
External ID | Customer No from Business Central |
Sales Order
Navigate to Microsoft Dynamics 365 Business Central → Sales → Sales Orders.
Use the Sales Order No as the External ID.
Enter it in the manual submission in iPaaS.com.
Product
Navigate to Microsoft Dynamics 365 Business Central → Sales → Items.
Use the Item No as the External ID.
Open a manual submission via Integration Monitoring → Manual Sync, complete the required fields, enter the Item No in the External ID field, and transfer the data.
Location
Search for Locations in Microsoft Dynamics 365 Business Central.
Use the Location Code as the External ID.
Open a manual submission via Integration Monitoring → Manual Sync, complete the required fields, enter the Location Code in the External ID field, and transfer the data.
Shipping Method
Search for Shipping Agents in Microsoft Dynamics 365 Business Central.
Open the Shipping Agents page.
Use the Shipping Agent Code as the External ID.
Open a manual submission via Integration Monitoring → Manual Sync, complete the required fields, enter the Shipping Agent Code in the External ID field, and transfer the data.
Transferring Data from iPaaS.com to Microsoft Dynamics 365 Business Central
To transfer data from iPaaS.com to Microsoft Dynamics 365 Business Central, you need the Internal ID (the iPaaS.com ID). This Internal ID is visible only within iPaaS.com.
Sales Order from iPaaS.com
Navigate to Data Management → Transactions in iPaaS.com.
Locate the transaction you want to transfer and click View Details.
Copy the Internal ID from the address bar.
Open a manual submission via Integration Monitoring → Manual Sync and complete the fields:
Field | Data |
System | Microsoft Dynamics 365 Business Central |
Mapping Collection | Dynamics Company Add/Update From iPaaS |
Scopes | Created/Updated |
iPaaS.com ID | Internal ID from the address bar |
Note: Follow the same procedure for the other data types supported in your integration.
Custom Fields
The integration between Microsoft Dynamics 365 Business Central and iPaaS.com supports custom fields on several data models, giving subscribers or their MiSP additional flexibility when synchronizing data.
Models that support custom fields:
Sales Order (Transaction) — both to and from iPaaS.com
Customer — both to and from iPaaS.com
Company — both to and from iPaaS.com
Sales Order Line (Transaction Line) — both to and from iPaaS.com
Order Tracking (Transaction Tracking) — to iPaaS.com only
Product — both to and from iPaaS.com
Adding Custom Fields (Business Central to iPaaS.com)
Create a custom field on the Business Central subscription in iPaaS.com.
Open your Microsoft Dynamics 365 Business Central subscription in iPaaS.com.
Add the desired custom field. For example, create a custom field named CatItemGroup on the Product model.
Create the matching custom field in iPaaS.com.
In iPaaS.com, create a custom field with the same name (for example, CatItemGroup).
Establish the field mapping.
Map the custom field between Business Central and iPaaS.com so the value transfers.
Transfer the data. Once the mapping is confirmed, run the transfer. The custom field value is then populated and stored on the iPaaS.com record.
Adding Custom Fields (iPaaS.com to Business Central)
Create a custom field on the Business Central subscription in iPaaS.com. For example, create a custom field named ProductTest on the Product model.
Map the data in iPaaS.com. Map the custom field to static or dynamic data.
Validate the transfer. Confirm the data flows from iPaaS.com to Business Central and that the field is populated correctly after the transfer.
Note: Custom fields can be configured for any of the supported models, enabling flexible integration scenarios.
Authentication Methods
The integration authenticates to Microsoft Dynamics 365 Business Central using OAuth 2.0. iPaaS.com uses the credentials entered in the subscription settings to obtain an access token, and refreshes the token automatically as it nears expiry. Each token is valid for 60 minutes (1 hour).
OAuth 2.0 Client Credentials Grant
The client credentials grant lets the integration authenticate using its own application credentials rather than a signed-in user. Permissions are granted directly to the application by an administrator, and the application is authorized to act on its own.
To obtain an access token, ensure the following values are correctly configured in the subscription settings:
Tenant Id: The directory (tenant) Id where the application is registered.
Grant Type: Must be set to client_credentials.
Client Id: The application (client) Id assigned during registration.
Client Secret: The secret value generated for the application. Store it securely, as it is shown only once.
Scope: The permissions or resource the application requests access to. Set it to https://api.businesscentral.dynamics.com/.default. The .default suffix requests the resource service generically without naming individual permissions.
After authentication, requests are scoped to the company named in the Company Name setting, so the records the integration reads and writes belong to that company.
Initialization Support
The following data types support initialization and can be transferred in bulk on the first connection:
Customer Category to iPaaS.com
Location to iPaaS.com
Shipping Method to iPaaS.com
All other data types must be configured and transferred individually during the integration process.
Throttling
Throttling prevents the Microsoft Dynamics 365 Business Central API from being overwhelmed by excessive calls, preserving performance during heavy data transfers.
The throttle fields are required, but their values are pre-populated by the integration settings. For more details, see Subscription Configuration – Edit.
Troubleshooting
Missing Credentials or API Configuration Errors
Ensure all required connection fields are completed, including Tenant Id, Client Id, Client Secret, and Scope.
Verify that the required permissions have been granted under API Permissions for Dynamics 365 Business Central.
OAuth Issues
For expired or invalid tokens, re-authorize the application in the Microsoft Entra Admin Center.
Ensure the Redirect URI matches exactly the one provided during application registration.
If transfers fail with authorization errors, confirm that the Grant Type is set to client_credentials and that the Company Name matches the company that holds your records.