Contents
Summary
Microsoft Dynamics 365 Business Central items can be transferred to iPaaS.com as products through the integration's polling schedule or through Manual Sync. Each Business Central item is captured as an iPaaS.com product with its SKU, name, description, default price, tax class, and weight, and the product status and tracking method are set so the product is active and tracked in iPaaS.com. The Business Central item type is translated to the matching iPaaS.com product type through a lookup translation. A single child collection captures the item's per-location inventory within the same transfer so the product and its inventory are recorded together.
This product family lets the integration keep a Business Central item and its on-hand inventory aligned with the subscriber's other connected systems. When the integration captures sales-price data, it formats the prices configured for a Business Central sales code into a custom field on the iPaaS.com product, which lets price information by customer group travel with the product.
ID Format
Manual Sync ID Format
When transferring a Business Central item from the iPaaS.com Manual Sync page, enter the item's internal record ID:
{{item_id}}The {{item_id}} value is the unique ID (a GUID) of the Business Central item.
Example:
6fbc9163-0295-ef11-8a6d-6045bdc8dfe6
The Business Central item number also resolves the record, so an item number can be entered in place of the GUID.
External ID Format
After a successful transfer, iPaaS.com saves the Business Central item number as the external ID on a dedicated external-ID record. This external ID links every subsequent transfer of the same item to the same iPaaS.com product rather than creating a duplicate. Keep the item number unique so repeated transfers update the existing product.
For the inventory child collection, iPaaS.com saves the Business Central location code combined with the item's internal record ID as the external ID, in the format {{location_code}}|{{item_id}} — for example, MAIN|6fbc9163-0295-ef11-8a6d-6045bdc8dfe6. This links each per-location inventory record to the same iPaaS.com inventory entry on every transfer.
Deleted Record Support
Outbound delete is not supported for the product or for its inventory child records. This family captures and updates products and inventory into iPaaS.com; it does not remove iPaaS.com records. Delete mappings are not included in the default templates, and deleting an item in Business Central does not remove the corresponding iPaaS.com product or inventory record. Subscribers who need to retire an iPaaS.com product should manage that on the iPaaS.com side.
Custom Field Support
Custom fields are supported on the parent product collection. They are not supported on the inventory child collection. This product family uses custom fields to capture formatted sales-price data by Business Central sales code — each sales code maps to its own custom field on the iPaaS.com product.
To capture a Business Central item value that is not already in the standard mapping list:
In Business Central, customize the relevant Web Service so the value is exposed in the item response. Subscribers or their MiSP can contact iPaaS.com Support for assistance customizing Business Central Web Services.
In iPaaS.com, create a custom field on the subscription that matches the field name and data type.
Map the new iPaaS.com custom field to the Business Central value on the parent product collection.
A custom field must exist on the iPaaS.com subscription before its mapping can store a value; an unmatched custom field is left unset. Capturing the sales-price custom fields additionally requires the sales-price presets described in the Mappings section and the Setup Requirements.
Mapping Collection Status
Status: Enabled
Trigger Events: Product Create, Product Update, Product Poll, plus Product Inventory Create and Product Inventory Update for the child collection. These collections use the product and product-inventory scope sets. Transfers happen automatically on the integration's polling schedule — there are no webhooks for this integration, so the integration periodically checks Business Central for new and changed items — and a Manual Sync can be run at any time. Whether a detected item creates a new iPaaS.com product or updates an existing one depends on the external-ID link (the saved item number), not on the change type — see ID Format.
Duplicate or Conflicting Mappings
Other collections operate on the same product or inventory data and may write the same kinds of records:
Add/Update Dynamics 365 Business Central Product FROM iPaaS.com writes products in the opposite direction (from iPaaS.com into Business Central) rather than capturing them.
Add/Update Dynamics 365 Business Central Product Inventory Standalone TO iPaaS.com captures the same per-location inventory on its own schedule rather than within the product transfer.
Before enabling these collections together, review their filters and Add/Update settings and decide which system is the source of truth for product and inventory data, so the same record is not written in conflicting directions.
Collision Handling
This integration does not provide configurable collision-handling methods for the product collections. There is no subscriber-selectable conflict-resolution option (such as Error, Remap and Link, or Update and No Link) on these collections. An incoming Business Central item is instead matched to its iPaaS.com product by SKU and linked by the saved external ID (the item number) — see Duplicate Matching. Keep the item number unique so repeated transfers update the same product rather than creating a duplicate.
Duplicate Matching
To avoid creating duplicate products in iPaaS.com, the integration matches an incoming Business Central item to an existing iPaaS.com product by SKU before recording a new one. When a match is found, the integration links the external ID to that existing product so subsequent transfers update it. When no match is found, a new iPaaS.com product is created and the external ID is saved against it.
The inventory child collection does not match against existing iPaaS.com records by content; its inventory records are linked by the saved external ID (the location code combined with the item ID) and are captured within the parent product's transfer.
Prerequisite Handling
When an item's inventory references a Business Central location that is not yet linked in iPaaS.com, the integration captures that location into iPaaS.com first so the inventory can resolve to it. This happens automatically within the product transfer; no other dependent records are transferred automatically. Inventory at a Business Central location that has no location code is not transferred.
Supported Child Collections
The parent Add/Update Dynamics 365 Business Central Product TO iPaaS.com collection captures the item header as an iPaaS.com product. One child collection captures the rest of the item within the same dispatch:
Child Collection | Purpose |
Add/Update Dynamics 365 Business Central Product Inventory TO iPaaS.com | Captures the item's per-location inventory as inventory on the iPaaS.com product. |
The child collection captures its records as part of the parent product's transfer; it is not synced on its own. To capture inventory independently, use the separate Add/Update Dynamics 365 Business Central Product Inventory Standalone TO iPaaS.com collection.
Lookup Translation
The parent collection's Type mapping translates the Business Central item type to the matching iPaaS.com product type through the Dynamics Product Status To iPaaS lookup translation. The default entries are:
Source (Microsoft Dynamics 365 Business Central) | Destination (iPaaS.com) |
Inventory | Physical |
Service | Service Items |
Non-Inventory | Non-Inventory Items |
A Business Central item type that has no matching entry in the lookup translation is not converted, so the product type is left unset for that item. Subscribers or their MiSP should confirm the lookup translation covers every item type in use before relying on this collection.
System Caveats
Microsoft Dynamics 365 Business Central Caveats
Item number is required: the item number must be present on the Business Central record. It is used as the product SKU and name, and it is saved as the external ID that links the item to its iPaaS.com product.
Sales price configuration: capturing the sales-price custom fields requires sales prices to be configured in Business Central with the sales codes named in the sales-price presets.
Location code required: inventory is captured only for Business Central locations that have a location code; quantities at unspecified locations are skipped.
iPaaS.com Caveats
SKU is the matching key: the integration matches an incoming item to an existing iPaaS.com product by SKU before recording a new one, then links the item number as the external ID that routes all subsequent transfers for that product.
Product type translation: Business Central item types are translated to iPaaS.com product types through a lookup translation. A type with no entry in the lookup translation is not converted — see Lookup Translation.
Same value for available and on-hand: the same Business Central remaining-quantity value at a location is recorded as both the available quantity and the on-hand quantity on the iPaaS.com inventory record.
Location linking: the Business Central location is resolved to its matching iPaaS.com location through a dedicated external-ID link. When a linked location is not found, the integration captures the location into iPaaS.com first so the inventory can be recorded against it.
Custom fields must exist first: a mapped custom field stores a value only when a custom field of the same name exists on the iPaaS.com subscription; otherwise the value is not stored.
Setup Requirements
Microsoft Dynamics 365 Business Central Configuration
Enable Web Services for Items, Item Card, Item Categories, and Customer Price Groups so the integration can read item, category, and sales-price data.
To capture per-location inventory, also enable Web Services for Items by Location and configure each inventory location with a location code.
If sales-price custom fields are used, configure sales prices in Business Central with the sales codes named in the sales-price presets.
Authentication uses OAuth 2.0; ensure credentials are stored securely in the iPaaS.com credential manager.
For the full installation walkthrough, see the Installation Instructions.
iPaaS.com Configuration
Confirm the Dynamics Product Status To iPaaS lookup translation covers every Business Central item type in use.
Create custom fields on the iPaaS.com subscription that match the Business Central field names and data types for any custom-field mappings in use, including each sales-code custom field.
For sales-price capture, set the Transfer Customer Price Groups preset to true, list the sales codes in the Sales Codes for Customer Price Groups preset (comma-separated), and set both the Sales Price Field Separator and Sales Price Record Delimiter presets. Each sales code must also exist in iPaaS.com as a Customer Category with a linked external ID. Use the Exclude Expired Rules preset to omit sales prices whose ending date has passed.
Ensure each Business Central location used for inventory is linked to an iPaaS.com location, or allow the integration to capture it during the product transfer.
Subscribers or their MiSP can contact iPaaS.com Support for assistance configuring Business Central Web Services.
Integration Flow
An item is created or updated in Business Central.
The integration detects the item on its polling schedule, or a subscriber triggers a Manual Sync using the item's internal record ID (or item number).
iPaaS.com authenticates with Business Central using OAuth 2.0 and reads the item, its per-location inventory, and — when sales-price transfer is enabled — its sales prices for the configured sales codes.
The integration matches the item to an existing iPaaS.com product by SKU; if a match is found it links the external ID to that product, otherwise it prepares to create a new product.
For each inventory location not yet linked in iPaaS.com, the integration captures the Business Central location into iPaaS.com first so the inventory can resolve to it.
The parent collection records the product: SKU, name, description, default price, tax class, weight, translated product type, status, tracking method, and any sales-price custom fields.
The inventory child collection records each per-location inventory entry with its iPaaS.com location, available quantity, on-hand quantity, and cost.
The iPaaS.com product is created on the first transfer or updated on subsequent transfers, matched by the saved external ID (the item number).
Transfer status and any errors are recorded in the iPaaS.com Dashboard under Integration Monitoring and the Error Logs.
Mappings
Add/Update Dynamics 365 Business Central Product TO iPaaS.com (Parent)
iPaaS.com data type: Product
This collection has no mapping filter, so every Business Central item it processes is captured. It records the product header and is the parent of the inventory child collection below.
Mapping Type | Source Field (Microsoft Dynamics 365 Business Central) | Destination Field (iPaaS.com) | Description |
Field |
| Sku | Required. The product SKU, taken from the Business Central item number. It is saved as the external ID and is the key used to match the item to its iPaaS.com product on every transfer. Keep the item number unique. |
Field |
| Name | Required. The product name, taken from the Business Central item number so the product always has a name. To use a different value, adjust this mapping to read the Business Central item description instead. |
Lookup Translation | Business Central item type, translated through the Dynamics Product Status To iPaaS lookup translation | Type | Required. Translates the Business Central item type to the matching iPaaS.com product type. For example, an Inventory item translates to a physical product type and a Service item translates to a service product type. A type with no matching entry is not converted — see Lookup Translation. |
Static |
| Status | Required (designed constant). Sets the product status to a fixed |
Static |
| TrackingMethod | Required (designed constant). Sets the product tracking method to a fixed |
Field |
| Description | Recommended. The product description, taken from the Business Central item description. Left unset when the item has no description. |
Field |
| DefaultPrice | Recommended. The product default price, taken from the Business Central item unit price. Left unset when the item has no unit price. |
Field |
| TaxClass | Recommended. The product tax class, taken from the Business Central item tax group code. Left unset when the item has no tax group code. |
Field |
| Weight | Recommended. The product weight, taken from the Business Central item net weight. Left unset when the item has no net weight. |
Dynamic Formula |
| Sales Code A1141DN Data (MSD) (Custom Field) | Recommended. Captures the Business Central sales prices for the named sales code into a custom field, formatted as a delimited string. Populated only when sales-price transfer is enabled and configured, and when the sales code exists in iPaaS.com as a Customer Category with a linked external ID. See the note below on the sales code value and the sales-price presets in Setup Requirements. |
Note on the sales code value. A1141DN is an example sales code. Replace it with a sales code configured in your Business Central company and listed in the Sales Codes for Customer Price Groups preset, or remove this custom field mapping if sales-price capture is not needed.
Add/Update Dynamics 365 Business Central Product Inventory TO iPaaS.com (Child)
iPaaS.com data type: Inventory
This collection is a child of the Product parent. It has no mapping filter. It captures the item's per-location inventory and records each location as inventory on the matching iPaaS.com product. Inventory is captured only for Business Central locations that have a location code; quantities at unspecified locations are skipped. Custom fields are not supported on this collection.
Mapping Type | Source Field (Microsoft Dynamics 365 Business Central) | Destination Field (iPaaS.com) | Description |
Dynamic Formula |
| LocationId | Required. Resolves the Business Central location code to its Business Central location, then to the matching iPaaS.com location, so the inventory is recorded against the correct location. The Business Central location must be linked to an iPaaS.com location; when no link exists, the integration captures the location into iPaaS.com first. Inventory at a location with no code is not transferred. |
Field |
| QtyAvailable | Required. The available quantity, taken from the Business Central remaining quantity at the location. |
Field |
| QtyOnHand | Required. The on-hand quantity, taken from the Business Central remaining quantity at the location. The same remaining-quantity value is recorded as both the available quantity and the on-hand quantity. |
Dynamic Formula |
| Dynamics Cost | Recommended. The unit cost, taken from the parent item. Left unset when the parent item has no unit cost. |
Error Handling
For the complete catalog of error messages this integration can produce, see the Error Messages article. The conditions most relevant to the product transfer are:
Missing item number: The item number is used as the SKU and name and is saved as the external ID that links each transfer to its iPaaS.com product. An item with no number cannot be captured. Resolution: ensure each Business Central item carries a unique item number before transferring.
Unconverted product type: When the Business Central item type has no matching entry in the Dynamics Product Status To iPaaS lookup translation, the product type is left unset. Resolution: add the missing item type to the lookup translation — see Lookup Translation.
Skipped inventory location: Inventory at a Business Central location with no location code is not transferred. Resolution: configure each inventory location with a location code in Business Central.
Unlinked sales code: Sales-price data is captured only when the sales code exists in iPaaS.com as a Customer Category with a linked external ID; otherwise no sales-price data is captured for that code and the custom field is left unset. Resolution: create the matching Customer Category in iPaaS.com or remove the sales-code custom field mapping.
Errors and transfer status for every product transfer are recorded in the iPaaS.com Dashboard under Integration Monitoring and the Error Logs.
Validation Rules
Item number present: the Business Central item must carry an item number; it becomes the SKU, name, and external ID.
Type translation: the product type is set only when the Business Central item type has a matching entry in the lookup translation.
Inventory location: an inventory record is captured only for a Business Central location that has a location code.
Location linking: the Business Central location must resolve to an iPaaS.com location; the integration captures it first when no link exists.
Sales-price capture: sales-price custom fields are populated only when sales-price transfer is enabled and configured and the sales code is linked as a Customer Category in iPaaS.com.
Testing and Validation
Test Scenarios
Valid product transfer. Create or update a Business Central item with a description, unit price, tax group code, net weight, and per-location inventory, then transfer it (by polling or Manual Sync). Confirm the iPaaS.com product is created with the correct SKU, name, translated type, status, tracking method, and recommended fields, and that inventory is captured per location.
Product type translation. Transfer items of type Inventory, Service, and Non-Inventory. Confirm each translates to the expected iPaaS.com product type, and that an item type missing from the lookup translation leaves the product type unset.
Duplicate matching by SKU. Transfer an item whose SKU already exists as an iPaaS.com product with no external-ID link. Confirm the integration links to the existing product rather than creating a duplicate.
Inventory location prerequisite. Transfer an item whose inventory references a Business Central location not yet linked in iPaaS.com. Confirm the integration captures the location into iPaaS.com first and records the inventory against it.
Missing location code. Transfer an item with inventory at a location that has no location code. Confirm that inventory is skipped and the rest of the product transfers.
Sales-price custom fields. Configure the sales-price presets and link a sales code as a Customer Category in iPaaS.com, then transfer an item that has sales prices for that code. Confirm the formatted sales-price value is stored on the matching custom field, and that an unlinked sales code leaves the field unset.
Repeat transfer / external ID. Transfer the same item twice. Confirm the second transfer updates the existing iPaaS.com product (matched by item number) rather than creating a duplicate.
Validation Checklist
The Business Central item carries a unique, non-empty item number.
All required Web Services are enabled in Business Central, including Items by Location for inventory.
The Dynamics Product Status To iPaaS lookup translation covers every item type in use.
Each inventory location is configured with a location code and linked to an iPaaS.com location.
Custom fields exist on the iPaaS.com subscription for every custom-field mapping in use, matching the Business Central field names and types.
For sales-price capture, the sales-price presets are set and each sales code is linked as a Customer Category in iPaaS.com.
Additional Notes
The product SKU and name are both taken from the Business Central item number by default; adjust the Name mapping to use the item description if a descriptive name is preferred.
The same Business Central remaining-quantity value at a location is recorded as both the available quantity and the on-hand quantity on the iPaaS.com inventory record.
Custom fields are supported on the parent product collection only; the inventory child collection does not support custom fields.
Outbound delete is not supported for the product or its inventory; deletions in Business Central do not propagate to iPaaS.com.
Related Documents
Connections and Settings (pending publication)
Known Limitations (pending publication)