Contents
Summary
Microsoft Dynamics 365 Business Central customer price groups can be transferred to iPaaS.com as customer categories through the integration's polling schedule or through Manual Sync. Each Business Central customer price group is captured as one iPaaS.com customer category: the category's name is set from the Business Central price group code, and its description is set from the Business Central price group description.
Capturing customer price groups as iPaaS.com customer categories lets the subscriber link and keep pricing groups in sync across their connected systems. The category resolved from a Business Central customer price group is also used when product price-group sales prices are captured, so transferring customer categories first establishes the categories that downstream product pricing can reference.
This is a single collection with no child collections. It reads from Business Central only; it does not write customer categories back into Business Central.
ID Format
Manual Sync ID Format
When transferring a Business Central customer price group from the iPaaS.com Manual Sync page, enter the Business Central customer price group code as the customer category identifier:
{{group_code}}The {{group_code}} value is the Business Central customer price group code. Enter that code into the EXTERNAL ID input field on the iPaaS.com Manual Sync page.
Example:
Retail
External ID Format
After a successful transfer, iPaaS.com saves the Business Central customer price group code as the external ID on a dedicated external-ID record. This external ID links every subsequent transfer of the same price group to the same iPaaS.com customer category rather than creating a duplicate. Keep the price group code unique so repeated transfers update the existing customer category.
Deleted Record Support
Outbound delete is not supported for the customer category. This collection captures and updates customer categories into iPaaS.com; it does not remove iPaaS.com records. Delete mappings are not included in the default templates, and deleting a customer price group in Business Central does not remove the corresponding iPaaS.com customer category. Subscribers who need to retire an iPaaS.com customer category should manage that on the iPaaS.com side.
Custom Field Support
Custom fields are not supported for the customer category collection. The integration does not expose a custom-field mechanism for this collection type and direction, and the default template maps only the standard category name and description shown below.
Mapping Collection Status
Status: Enabled
Trigger Events: Customer Category Create, Customer Category Update, Customer Category Poll. This collection uses the customer 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 customer price groups — and a Manual Sync can be run at any time. Whether a detected price group creates a new iPaaS.com customer category or updates an existing one depends on the external-ID link (the saved price group code), not on the change type — see ID Format.
Duplicate or Conflicting Mappings
No other collection in this integration writes the same Business Central customer price group into iPaaS.com, so there is no conflicting collection to coordinate with for customer category data.
Collision Handling
This integration does not provide configurable collision-handling methods for the customer category collection. There is no subscriber-selectable conflict-resolution option (such as Error, Remap and Link, or Update and No Link) on this collection. Customer price groups are instead linked to their iPaaS.com customer category by the saved external ID (the price group code) and by the duplicate-matching behavior described below.
Duplicate Matching
To avoid creating duplicate customer categories in iPaaS.com, the integration matches an incoming Business Central customer price group to an existing iPaaS.com customer category before recording a new one. When no external-ID link already exists for the price group, the integration looks up an existing iPaaS.com customer category whose name matches the Business Central price group code; if one is found, the integration links the external ID (the price group code) to that existing category instead of creating a duplicate. This matching is by the price group code, so the code must be present on the Business Central price group.
Supported Child Collections
This collection has no child collections. It captures customer category records only.
System Caveats
Microsoft Dynamics 365 Business Central Caveats
Code as identifier: the Business Central customer price group 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 price group for the transfer to link correctly.
Source scope: this collection reads customer price groups. Other Business Central price or discount configurations are not captured by this collection.
iPaaS.com Caveats
Name from code, description from description: the iPaaS.com customer category name is set from the Business Central price group code, and the description is set from the Business Central price group description. If the price group description is empty in Business Central, the iPaaS.com description is left unset.
Pricing-group role: customer categories captured from Business Central customer price groups represent pricing groups. The resolved category is also used when capturing customer price-group sales prices on the product collection, so the customer categories established here are referenced by downstream product pricing.
Setup Requirements
Microsoft Dynamics 365 Business Central Configuration
Enable Web Services for Customer Price Groups so the integration can read customer price group records.
Ensure each customer price group carries a valid code; the code is the identifier used to match the category to its iPaaS.com record.
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 additional iPaaS.com configuration is required for this collection beyond the standard integration setup. Manual Sync is always available — enter the Business Central customer price group code on the Manual Sync page to transfer a specific category.
Subscribers or their MiSP can contact iPaaS.com Support for assistance configuring Business Central Web Services.
Integration Flow
A customer price group is created or updated in Business Central.
The integration detects the price group on its polling schedule, or a subscriber triggers a Manual Sync using the Business Central price group code.
iPaaS.com authenticates with Business Central using OAuth 2.0 and reads the customer price group.
The collection records the customer category: name from the Business Central price group code and description from the Business Central price group description.
Before recording a new category, the integration checks for an existing iPaaS.com customer category linked by external ID, and otherwise matches by the price group code, so an existing category is updated rather than duplicated.
The iPaaS.com customer category is created on the first transfer or updated on subsequent transfers, matched by the saved external ID (the price group 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 Customer Category TO iPaaS.com
iPaaS.com data type: Customer Category
This collection has no mapping filter, so every Business Central customer price group it processes is captured.
Mapping Type | Source Field (Microsoft Dynamics 365 Business Central) | Destination Field (iPaaS.com) | Description |
Field |
| Name | Required. The iPaaS.com customer category name, taken from the Business Central customer price group code. The code is saved as the external ID and is the key used to match the price group to its iPaaS.com customer category on every transfer. Keep the price group code unique. |
Field |
| Description | Recommended. The iPaaS.com customer category description, taken from the Business Central customer price group description. Left unset when the price group 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 customer category transfer are:
Missing price group code: the price group code is mapped to the customer category name and saved as the external ID; it is the key that links each transfer to its iPaaS.com customer category. A price group with no code cannot be linked. Resolution: ensure each Business Central customer price group has a valid code before transferring.
Duplicate or non-unique code: the price group code is the matching key. A non-unique code can cause a transfer to update an unintended customer category. Resolution: keep customer price group codes unique so each transfer updates the intended customer category, or update the existing record rather than creating a new one.
Errors and transfer status for every customer category transfer are recorded in the iPaaS.com Dashboard under Integration Monitoring and the Error Logs.
Validation Rules
Code present: the customer price group code must be present; it is mapped to the customer category name and saved as the external ID.
Code unique: the code is the matching key, so it should be unique to keep repeated transfers updating the intended customer category.
Description: the description should be present for clarity but is not required; an empty description leaves the iPaaS.com description unset.
Testing and Validation
Test Scenarios
Valid customer category transfer. Transfer a Business Central customer price group that has a code and description (by polling or Manual Sync). Confirm the iPaaS.com customer category is created with its name set from the code and its description set from the price group description.
Update an existing category. Change a customer price group description in Business Central and transfer it again. Confirm the change is reflected on the existing iPaaS.com customer category rather than creating a new one.
ID format. From the Manual Sync page, transfer a specific price group by entering its code and confirm the correct customer category is captured.
Repeat transfer / external ID. Transfer the same price group twice. Confirm the second transfer updates the existing iPaaS.com customer category (matched by the price group code) rather than creating a duplicate.
Duplicate matching. Transfer a price group whose code matches the name of a customer category that already exists in iPaaS.com. Confirm the integration links to the existing category rather than creating a duplicate.
Empty description. Transfer a price group that has a code but no description. Confirm the iPaaS.com customer category is created with its description left unset.
Validation Checklist
The Business Central customer price group carries a valid, unique code.
Web Services are enabled for Customer Price Groups in Business Central.
OAuth 2.0 credentials are stored in the iPaaS.com credential manager.
Customer price group descriptions are populated where a description is wanted on the iPaaS.com customer category.
Additional Notes
The customer category name is always set from the Business Central price group code, so the code is both the displayed name and the matching key — keep it meaningful and unique.
Customer categories captured here represent pricing groups and are referenced when product price-group sales prices are captured, so transferring customer categories establishes the categories that downstream product pricing relies on.
Outbound delete is not supported; deleting a customer price group in Business Central does not remove the corresponding iPaaS.com customer category.
Related Documents
Connections and Settings (pending publication)
Known Limitations (pending publication)