Contents
Summary
Microsoft Dynamics 365 Business Central item categories can be transferred to iPaaS.com as product categories through the integration's polling schedule or through Manual Sync. Each Business Central item category is captured as an iPaaS.com product category, with the category name taken from the Business Central category code and the category description taken from the Business Central category description.
This collection lets subscribers keep their Business Central item categories aligned with the product categories in iPaaS.com, so categories can be referenced consistently across the subscriber's connected systems. The transfer is one-directional: it captures and updates categories into iPaaS.com from Business Central.
ID Format
Manual Sync ID Format
When transferring a Business Central item category from the iPaaS.com Manual Sync page, enter the Business Central item category code in the External ID input field:
{{category_code}}The {{category_code}} value is the item category code as it appears on the Business Central item category record.
Example:
FURN
External ID Format
After a successful transfer, iPaaS.com saves the Business Central item category code as the external ID on a dedicated external-ID record. This external ID links every subsequent transfer of the same category to the same iPaaS.com product category rather than creating a duplicate. Keep the item category code unique so repeated transfers update the existing category.
Deleted Record Support
Outbound delete is not supported for the product category. This collection captures and updates categories into iPaaS.com; it does not remove iPaaS.com records. Deleting an item category in Business Central does not remove the corresponding iPaaS.com product category. Subscribers who need to retire an iPaaS.com product category should manage that on the iPaaS.com side.
Custom Field Support
Custom fields are not supported for the product category collection in this direction. All transferred values are captured through the standard category mappings listed below, and there are no custom-field mappings on this collection.
Mapping Collection Status
Status: Enabled
Sync Type: Add
Trigger Events: Category Create, Category Update, Poll Category. This collection uses the product category scope set. 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 item categories — and a Manual Sync can be run at any time. Whether a detected category creates a new iPaaS.com product category or updates an existing one depends on the external-ID link (the saved category code), not on the change type — see ID Format.
Duplicate or Conflicting Mappings
No other collection in this integration writes the same Business Central item category into iPaaS.com, so there is no conflicting collection to coordinate with for product category data.
Collision Handling
This integration does not provide configurable collision-handling methods for the product category collection. There is no subscriber-selectable conflict-resolution option (such as Error, Remap and Link, or Update and No Link) on this collection. Categories are instead matched to their iPaaS.com product category by the saved external ID (the category code) — see Duplicate Matching. Keep the item category code unique so repeated transfers update the same product category rather than creating a duplicate.
Duplicate Matching
To avoid creating duplicate categories in iPaaS.com, the integration matches an incoming Business Central item category to an existing iPaaS.com product category by its code before recording a new one. When a matching iPaaS.com product category is found by code, the integration links the external ID to that existing record so the transfer updates it rather than creating a second category. This duplicate-matching behavior does not auto-transfer any related record; it only links the incoming category to a category that already exists in iPaaS.com.
Supported Child Collections
None. This collection captures the product category record only, and it has no child collections.
System Caveats
Microsoft Dynamics 365 Business Central Caveats
Code as identifier: the Business Central item category code is the value used to match the category to its iPaaS.com record and is saved as the external ID; it must be present on the Business Central item category.
Name comes from the code: the iPaaS.com product category name is set from the Business Central item category code, not from the Business Central category description. Subscribers who expect the iPaaS.com category name to read as a descriptive label should be aware that the code is what populates the name.
iPaaS.com Caveats
Description preserved when present: the iPaaS.com product category description is set from the Business Central item category description. If the category description is empty in Business Central, the iPaaS.com description is left unset.
Category code is the routing key: the item category code must be present on the Business Central record for the transfer to link correctly. It is saved as the external ID that routes all subsequent transfers for that category.
Setup Requirements
Microsoft Dynamics 365 Business Central Configuration
Enable Web Services for Item Categories so the integration can read item category records.
Ensure each item category to be transferred has a valid code; the code is the matching key and is required.
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
No collection-specific presets are required for the product category transfer beyond the standard integration setup.
Subscribers or their MiSP can contact iPaaS.com Support for assistance configuring Business Central Web Services.
Integration Flow
An item category is created or updated in Business Central.
The integration detects the category on its polling schedule, or a subscriber triggers a Manual Sync by entering the item category code.
iPaaS.com authenticates with Business Central using OAuth 2.0 and reads the item category.
The integration checks for an existing iPaaS.com product category that matches the Business Central category code, and links to it if one is found.
The category data is mapped to the iPaaS.com product category format — the name from the Business Central category code and the description from the Business Central category description.
The iPaaS.com product category is created on the first transfer or updated on subsequent transfers, matched by the saved external ID (the category code).
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 Category TO iPaaS.com
iPaaS.com data type: Product Category
This collection captures the Business Central item category as an iPaaS.com product category. It has no mapping filter, so every Business Central item category this collection processes is captured.
Mapping Type | Source Field (Microsoft Dynamics 365 Business Central) | Destination Field (iPaaS.com) | Description |
Field |
| Name | Required. The iPaaS.com product category name, taken from the Business Central item category code. The code is saved as the external ID and is the key used to match the category to its iPaaS.com record on every transfer. Keep the item category code unique. |
Field |
| Description | Recommended. The iPaaS.com product category description, taken from the Business Central item category description. Left unset when the Business Central category has no description. |
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 category transfer are:
Missing category code: The item category code is taken into the iPaaS.com product category name and saved as the external ID. A Business Central item category with no code cannot be linked or matched. Resolution: ensure each Business Central item category carries a valid code before transferring.
Duplicate category code: The category code is the matching key. A non-unique code can cause a transfer to update an unintended product category. Resolution: ensure item category codes are unique so repeated transfers update the intended record rather than colliding with another.
Errors and transfer status for every category transfer are recorded in the iPaaS.com Dashboard under Integration Monitoring and the Error Logs.
Validation Rules
Code required: the item category code must be present; it populates the iPaaS.com product category name and is saved as the external ID used for matching.
No filter: this collection has no mapping filter, so every item category it processes is captured.
Description optional: the description is captured when present and left unset when the Business Central category has no description.
Testing and Validation
Test Scenarios
Valid category transfer. Transfer a Business Central item category that has a code and a description (by polling or Manual Sync). Confirm the iPaaS.com product category is created with the name set from the category code and the description set from the category description.
Category without a description. Transfer a Business Central item category that has a code but no description. Confirm the iPaaS.com product category is created with the name set and the description left unset.
ID format. From the Manual Sync page, transfer a specific category by entering its item category code in the External ID field, and confirm the correct category is captured.
Repeat transfer / external ID. Transfer the same category twice. Confirm the second transfer updates the existing iPaaS.com product category (matched by category code) rather than creating a duplicate.
Duplicate matching. Transfer a Business Central item category whose code matches a product category that already exists in iPaaS.com. Confirm the integration links to the existing iPaaS.com product category rather than creating a second one.
Validation Checklist
The Business Central item category carries a unique, non-empty code.
Web Services for Item Categories are enabled in Business Central.
Descriptions are populated on item categories where a category description is wanted in iPaaS.com.
Additional Notes
The iPaaS.com product category name is populated from the Business Central item category code rather than the category description; subscribers who expect a descriptive name should account for this.
This collection captures the category name and description; it does not set a parent-category relationship in iPaaS.com.
Outbound delete is not supported; deletions in Business Central do not propagate to iPaaS.com.
Related Documents
Connections and Settings (pending publication)
Known Limitations (pending publication)