Contents
Summary
Product records can be sent from iPaaS.com into Microsoft Dynamics 365 Business Central through the Add/Update Dynamics 365 Business Central Product FROM iPaaS.com collection. Each transfer creates or updates an item record in the target Business Central company. The mapping populates the item number, description, unit price, tax group code, and net weight, and sets the item type, base unit of measure, order tracking policy, and the general product and inventory posting groups that control how the item is classified and posted in Business Central.
Whether an incoming product is created as a new item or updates an existing one is decided by whether the iPaaS.com product is already linked to a Business Central item, not by which event fired. Items sent through this collection are always created as an inventory-type item. The item number is the key that links, matches, and later updates the record, so it must be present and unique on every product sent.
ID Format
Manual Sync ID Format
When transferring a product from the iPaaS.com Manual Sync page, enter the iPaaS.com product record ID of the product to transfer.
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. The item is identified in Business Central by its item number — the No. field on the item card. This external ID routes every subsequent transfer of the same product to the existing Business Central item rather than creating a duplicate. An example item number value from Business Central is ITEM1001.
As a fallback, when no external-ID record exists yet and the iPaaS.com product SKU matches an existing Business Central item number, the records are linked automatically instead of creating a duplicate — see Duplicate Matching.
Deleted Record Support
Outbound delete is not supported for the item record. This collection creates and updates Business Central items from iPaaS.com; it does not remove Business Central records. Delete mappings are not included in the default templates, and deleting a product in iPaaS.com does not remove the corresponding Business Central item. Subscribers who need to retire a Business Central item should manage that on the Business Central side.
Custom Field Support
Custom fields are supported for this collection. To set a Business Central item field that is not already in the standard mapping list:
In Business Central, customize the relevant Web Service so it accepts the field on the item request. Subscribers or their MiSP can contact iPaaS.com Support for assistance customizing Business Central Web Services.
In iPaaS.com, create a custom field whose name matches the Business Central field name you want to populate.
Map the new custom field to a static or dynamic source.
Each such custom field name and value is included in the item record sent to Business Central as-is. The name must be a valid item field in your Business Central environment, or Business Central rejects the request.
Mapping Collection Status
Status: Enabled
Trigger Events: Product Create, Product Update. This collection uses the product scope set. In this direction, transfers dispatch automatically once subscribers or their MiSP subscribe to the iPaaS.com product outbound triggers — enable them in the subscription configuration's Outbound Data Flows section by subscribing to the product create and update events. Until those subscriptions are enabled, no automatic transfers occur, and a Manual Sync can be run at any time. Whether a transferred product is created as a new Business Central item or updates an existing one depends on whether the record is already linked to a Business Central item, not on which event fired.
Duplicate or Conflicting Mappings
Other collections also operate on the Business Central item and may write the same record:
Add/Update Dynamics 365 Business Central Product TO iPaaS.com captures items from Business Central into iPaaS.com — the opposite direction.
Before enabling these collections together, review their filters and Add/Update settings and decide which system is the source of truth for product data, so the same product is not written in conflicting directions.
Collision Handling
This integration does not provide configurable collision-handling methods for the product collection. There is no subscriber-selectable conflict-resolution option (such as Error, Remap and Link, or Update and No Link) on this collection. Products are instead matched to their Business Central record by the saved external ID (the item number), with a SKU-to-item-number fallback — see Duplicate Matching. Keep the item number (SKU) unique so repeated transfers update the same item rather than creating a duplicate.
Duplicate Matching
Before creating a new item, the integration checks whether the incoming product is already linked to a Business Central item. If it is not yet linked, the integration looks up an existing Business Central item whose item number matches the iPaaS.com product SKU. When a match is found, the iPaaS.com product is linked to that existing Business Central item instead of creating a duplicate. This SKU-based fallback runs only when no external-ID link already exists; once a product is linked, subsequent transfers route by the saved external ID.
Supported Child Collections
None. This collection writes the item record only. Per-location inventory is not written to Business Central in this direction; product inventory is captured into iPaaS.com by separate collections in the opposite direction.
System Caveats
Microsoft Dynamics 365 Business Central Caveats
Posting groups must already exist: the general product posting group and the inventory posting group are validated by Business Central against records that must already exist in your company. The collection ships with example values that will not match your company — replace each with a value configured in your Business Central setup before the first transfer, or the transfer fails when Business Central rejects the unknown value.
Base unit of measure must already exist: the base unit of measure ships with an example value and must match a unit of measure configured in your Business Central company, or Business Central rejects the item.
Item type: items created through this collection are set to the inventory type.
Description length: Business Central limits the item description, so a longer iPaaS.com description is truncated to fit.
iPaaS.com Caveats
SKU is the routing key: the product SKU populates the Business Central item number and is required for the transfer to link correctly. It is saved as the external ID that routes all subsequent transfers for that item, so it must be present and unique.
Custom fields must match a Business Central field name: a mapped custom field is sent to Business Central only when its name matches a valid Business Central item field. An unmatched field name causes Business Central to reject the request.
Setup Requirements
Microsoft Dynamics 365 Business Central Configuration
Enable Web Services for Items and Item Card so the integration can read and write item records.
The general product posting group, the inventory posting group, and the base unit of measure used by the mappings must exist in your Business Central company before the first transfer.
If custom fields are mapped, customize the relevant Web Service so it accepts them on the item request.
Authentication uses Business Central API credentials; ensure credentials are stored securely in the iPaaS.com credential manager.
For the full installation walkthrough, see the Installation Instructions.
iPaaS.com Configuration
Subscribe to the product create and update outbound triggers in the Outbound Data Flows section to enable automatic transfers.
Ensure each product to be transferred carries a unique, non-empty SKU.
Create custom fields whose names match the Business Central item field names for any custom-field mappings in use.
Subscribers or their MiSP can contact iPaaS.com Support for assistance configuring Business Central Web Services.
Integration Flow
A product is created or updated in iPaaS.com.
The transfer dispatches automatically when the product create or update outbound trigger is subscribed in Outbound Data Flows, or a subscriber triggers a Manual Sync using the iPaaS.com product record ID.
iPaaS.com authenticates with Business Central and checks whether the product is already linked to a Business Central item. If it is not linked, the integration looks up an existing item by SKU and links to it when a match is found.
The item description is truncated to the Business Central maximum length if needed.
The product fields are mapped to the Business Central item, including the item number, description, unit price, tax group code, net weight, item type, base unit of measure, order tracking policy, and the general product and inventory posting groups.
Any mapped custom fields whose names match valid Business Central item fields are added to the item request.
The item is created on the first transfer or updated on a subsequent transfer, 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 FROM iPaaS.com
iPaaS.com data type: Product
This collection has no mapping filter, so every product record sent through it is processed. It writes a single Business Central item record.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Microsoft Dynamics 365 Business Central) | Description |
Field |
| No | Required. Sets the Business Central item number from the iPaaS.com product SKU. This is the key the integration uses to match, link, and later update the item, and it is saved as the external ID. The SKU must be present and unique, or the transfer fails. |
Dynamic Formula |
| Description | Recommended. Sets the Business Central item description from the iPaaS.com product description. Business Central limits the item description length, so a longer description is truncated to fit. Left unset when the product has no description. |
Field |
| UnitPrice | Recommended. Sets the Business Central item unit price from the iPaaS.com product default price. Left unset when the product has no default price. |
Field |
| TaxGroupCode | Recommended. Sets the Business Central item tax group code from the iPaaS.com product tax class. The tax group code should match an existing tax group in your Business Central company. Left unset when the product has no tax class. |
Field |
| NetWeight | Recommended. Sets the Business Central item net weight from the iPaaS.com product weight. Left unset when the product has no weight. |
Static |
| Type | Required (designed constant). Sets the Business Central item type so items created through this collection are inventory-type items. Change this static value to another Business Central item type (for example, Service or Non-Inventory) if a different classification is required. |
Static |
| OrderTrackingPolicy | Recommended. Sets the Business Central item order tracking policy. The shipped value is a Business Central order tracking policy option; change it if your company uses a different policy for these items. |
Static |
| BaseUnitOfMeasure | Required. Sets the Business Central item base unit of measure. The base unit of measure is validated by Business Central and must already exist in your company. The shipped value is an example — confirm a unit of measure named PCS exists in your Business Central company, or change this static value to an existing unit of measure code. The first transfer fails without it. See Error Handling. |
Static |
| GenProdPostingGroup | Required. Sets the general product posting group, which controls how the item's transactions post. The posting group is validated by Business Central and must already exist in your company. The shipped value is an example — confirm a Gen. Prod. Posting Group named RETAIL exists in your Business Central company, or change this static value to an existing posting group code. The first transfer fails without it. See Error Handling. |
Static |
| InventoryPostingGroup | Required. Sets the inventory posting group, which controls how the item's inventory posts to the general ledger. The posting group is validated by Business Central and must already exist in your company. The shipped value is an example — confirm an Inventory Posting Group named RESALE exists in your Business Central company, or change this static value to an existing posting group code. The first transfer fails without it. See Error Handling. |
Note on the posting-group and unit-of-measure values. The values PCS, RETAIL, and RESALE shipped with this collection are examples and will not match an arbitrary Business Central company. Each must be confirmed or replaced during implementation, because Business Central validates them against existing records and rejects the item if the value does not exist. Subscribers or their MiSP should confirm or substitute these values before the first transfer.
Error Handling
For the complete catalog of error messages this integration can produce, see the Error Messages article. The errors most relevant to the product transfer are:
Missing SKU: The product SKU sets the Business Central item number and is required. A product transferred without a SKU cannot be written, and the transfer stops. Resolution: ensure each product has a valid, non-empty SKU in iPaaS.com before transferring.
Posting group does not exist: The general product posting group or the inventory posting group on the item does not exist in your Business Central company, and Business Central rejects the item. Resolution: confirm the Gen. Prod. Posting Group and Inventory Posting Group values used by the mappings exist in your Business Central setup, or change the static values to existing posting group codes, then re-transfer.
Base unit of measure does not exist: The base unit of measure on the item does not match a unit of measure configured in your Business Central company, and Business Central rejects the item. Resolution: confirm the base unit of measure value exists in your Business Central company, or change the static value to an existing unit of measure code, then re-transfer.
Custom field not accepted: A mapped custom field name is not a valid Business Central item field, and Business Central rejects the request. Resolution: confirm the custom field name matches a valid Business Central item field and that the Web Service is customized to accept it.
Errors and transfer status for every product transfer are recorded in the iPaaS.com Dashboard under Integration Monitoring and the Error Logs.
Validation Rules
SKU presence: the product SKU must be present and unique; it sets the Business Central item number and is the key that links and routes every transfer.
Posting group existence: the general product posting group and the inventory posting group used by the mappings must already exist in your Business Central company before the first transfer.
Base unit of measure existence: the base unit of measure used by the mapping must match an existing unit of measure in your Business Central company.
Item type: items are created as the inventory type unless the static value is changed.
Custom field validity: any mapped custom field name must be a valid Business Central item field, or Business Central rejects the request.
Testing and Validation
Test Scenarios
Valid product transfer. Transfer a product from iPaaS.com with a unique SKU, a description, a default price, a tax class, and a weight, with the posting groups and base unit of measure set to values that exist in your Business Central company. Confirm a Business Central item is created with the expected number, description, price, tax group, weight, item type, base unit of measure, order tracking policy, and posting groups.
Long description. Transfer a product whose description is longer than the Business Central maximum. Confirm the description is truncated to fit and the item is created without error.
Posting group validation. Transfer a product while a posting group static value does not exist in your Business Central company. Confirm the transfer stops with a posting-group error, then confirm that correcting the static value to an existing posting group and re-transferring succeeds.
Base unit of measure validation. Transfer a product while the base unit of measure static value does not exist in your Business Central company. Confirm the transfer stops, then confirm that correcting the value to an existing unit of measure and re-transferring succeeds.
Duplicate SKU / external-ID linking. Transfer a product whose SKU matches an existing Business Central item number that is not yet linked. Confirm the iPaaS.com product is linked to that existing item instead of creating a duplicate.
Repeat transfer / update. Transfer the same product twice. Confirm the second transfer updates the existing Business Central item (matched by item number) rather than creating a duplicate.
Custom field. Map a custom field whose name matches a valid Business Central item field and transfer a product. Confirm the value is written to that field on the Business Central item.
Validation Checklist
Each product carries a unique, non-empty SKU.
Web Services for Items and Item Card are enabled in Business Central.
The general product posting group, the inventory posting group, and the base unit of measure used by the mappings exist in your Business Central company.
The product create and update outbound triggers are subscribed in Outbound Data Flows if automatic transfers are needed.
Custom fields whose names match Business Central item fields exist for any custom-field mappings in use.
Additional Notes
Items sent through this collection are always created as an inventory-type item with a fixed base unit of measure and posting groups. Adjust the Type, BaseUnitOfMeasure, GenProdPostingGroup, and InventoryPostingGroup mappings if a different classification is required.
The posting-group and base-unit-of-measure values are validated by Business Central against existing records, so they behave as setup prerequisites rather than free-text values.
Outbound delete is not supported for the item; deleting a product in iPaaS.com does not remove the corresponding Business Central item.
Related Documents
Connections and Settings (pending publication)
Known Limitations (pending publication)