Contents
Summary
Microsoft Dynamics 365 Business Central shipping methods can be transferred to iPaaS.com so that shipping methods stay aligned across the subscriber's connected systems. Each Business Central shipping method is captured as an iPaaS.com shipping method record: the iPaaS.com shipping method name is set from the Business Central shipping method code, and the iPaaS.com description is set from the Business Central shipping method name.
This is a single-collection family with no child collections. Records are transferred through bulk initialization, through the integration's polling schedule, and through Manual Sync. Because the Business Central code maps to the iPaaS.com name rather than to a like-named field, the code is the value that links a Business Central shipping method to its iPaaS.com record on every transfer.
ID Format
Manual Sync ID Format
When transferring a Business Central shipping method from the iPaaS.com Manual Sync page, enter the Business Central shipping method code:
{{shippingmethod_code}}The shipping method code uniquely identifies the shipping method record within Microsoft Dynamics 365 Business Central. It is found on the shipping agent record in Business Central.
Example:
TRUCK
External ID Format
After a successful transfer, iPaaS.com saves the Business Central shipping method code as the external ID on a dedicated external-ID record. This external ID links every subsequent transfer of the same shipping method to the same iPaaS.com shipping method record rather than creating a duplicate. Keep the shipping method code stable so repeated transfers update the existing record.
Deleted Record Support
Outbound delete is not supported for the shipping method record. This collection captures and updates shipping methods into iPaaS.com; it does not remove iPaaS.com records. Delete mappings are not included in the default templates, and deleting a shipping method in Business Central does not remove the corresponding iPaaS.com shipping method. Subscribers who need to retire an iPaaS.com shipping method should manage that on the iPaaS.com side.
Custom Field Support
Custom fields are not supported for the shipping method collection. The integration captures the shipping method code and name only; there is no mechanism to map additional Business Central shipping method values onto iPaaS.com custom fields for this collection.
Mapping Collection Status
Status: Enabled
Trigger Events: Shipping Method Create, Shipping Method Update, Shipping Method Poll. This collection uses the shipping method 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 shipping methods — and a Manual Sync can be run at any time. Whether a detected shipping method creates a new iPaaS.com record or updates an existing one depends on the external-ID link (the saved shipping method code), not on the change type — see ID Format.
This collection has no mapping filter, so every Business Central shipping method this collection processes is captured.
Duplicate or Conflicting Mappings
No other collection in this integration writes Business Central shipping methods into iPaaS.com, so there is no conflicting collection to coordinate with.
Collision Handling
This integration does not provide configurable collision-handling methods for the shipping method collection. There is no subscriber-selectable conflict-resolution option (such as Error, Remap and Link, or Update and No Link) on this collection. Shipping methods are instead matched to their iPaaS.com record by code — see Duplicate Matching.
Duplicate Matching
To avoid creating duplicate shipping methods in iPaaS.com, the integration first looks for an existing iPaaS.com shipping method linked to the Business Central shipping method code. If none is linked, it searches existing iPaaS.com shipping methods by name (the shipping method name in iPaaS.com is the Business Central code). When a match is found, the integration links the external ID to that existing record rather than creating a new one. Because matching is performed on the code, keep shipping method codes unique and stable in Business Central. Shipping methods that resolve to the same name in iPaaS.com are linked to a single iPaaS.com record rather than duplicated.
Supported Child Collections
This collection has no child collections. It captures shipping method records only.
System Caveats
Microsoft Dynamics 365 Business Central Caveats
Code as identifier: the Business Central shipping method code is the value used to match the shipping method to its iPaaS.com record; it must be present on the Business Central shipping method.
Field name mapping: the Business Central shipping method code maps to the iPaaS.com shipping method name, and the Business Central shipping method name maps to the iPaaS.com shipping method description. These are not one-to-one name matches.
iPaaS.com Caveats
Name is set from the code: the iPaaS.com shipping method name is set from the Business Central shipping method code, and the description is set from the Business Central shipping method name. If the shipping method name is empty in Business Central, the iPaaS.com description is left unset.
Matching is by name: shipping method matching is performed by name (the Business Central code). Shipping methods that resolve to the same name in iPaaS.com are linked to a single iPaaS.com shipping method record rather than duplicated.
Setup Requirements
Microsoft Dynamics 365 Business Central Configuration
Enable Web Services for Shipping Methods so the integration can read shipping method records.
Ensure each shipping method has a valid code, and a name if the description should be populated in iPaaS.com.
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 shipping method collection.
To load existing shipping methods in bulk, run bulk initialization for Shipping Methods from the iPaaS.com subscription settings (see Integration Flow).
Subscribers or their MiSP can contact iPaaS.com Support for assistance configuring Business Central Web Services.
Integration Flow
A shipping method is created or updated in Business Central.
The integration detects the shipping method on its polling schedule, a subscriber triggers a Manual Sync using the shipping method code, or a bulk initialization is run to load all shipping methods at once.
iPaaS.com authenticates with Business Central using OAuth 2.0 and reads the shipping method.
The integration checks for an existing iPaaS.com shipping method linked to the Business Central code, and if none is linked, searches existing iPaaS.com shipping methods by name (the code). A match is linked by external ID rather than duplicated.
The collection records the shipping method: the Business Central code as the iPaaS.com name, and the Business Central name as the iPaaS.com description.
The iPaaS.com shipping method is created on the first transfer or updated on subsequent transfers, matched by the saved external ID (the shipping method code).
Transfer status and any errors are recorded in the iPaaS.com Dashboard under Integration Monitoring and the Error Logs.
Bulk Initialization
To load existing Business Central shipping methods in a single pass, run bulk initialization for Shipping Methods from the iPaaS.com subscription settings by selecting the initialization control next to the Shipping Method entry. This reads all shipping method records from Business Central and transfers each one to iPaaS.com using the same mappings described below. Bulk initialization is only needed by subscribers who have chosen to integrate shipping methods, and is typically run once during initial setup or when a full resync is required; for subscribers not using this collection it has no effect.
Mappings
Add/Update Dynamics 365 Business Central Shipping Method TO iPaaS.com
iPaaS.com data type: Shipping Method
This collection has no mapping filter, so every Business Central shipping method it processes is captured.
Mapping Type | Source Field (Microsoft Dynamics 365 Business Central) | Destination Field (iPaaS.com) | Description |
Field |
| Name | Required. Sets the iPaaS.com shipping method name from the Business Central shipping method code. The code is the value saved as the external ID and used to match the Business Central shipping method to its iPaaS.com record on every transfer. The Business Central code maps to the iPaaS.com name; these are not one-to-one name matches. |
Field |
| Description | Recommended. Sets the iPaaS.com shipping method description from the Business Central shipping method name. Left unset when the Business Central shipping method has no name. The Business Central name maps to the iPaaS.com description; these are not one-to-one name matches. |
Error Handling
For the complete catalog of error messages this integration can produce, see the Error Messages article. The condition most relevant to the shipping method transfer is:
Duplicate shipping method name: A shipping method with the same name (the Business Central code) already exists in iPaaS.com. The integration handles this by linking the existing iPaaS.com shipping method to the Business Central code through an external ID rather than creating a duplicate. If the existing record should be updated rather than linked, confirm the external ID is correctly linked between Business Central and iPaaS.com.
Errors and transfer status for every shipping method transfer are recorded in the iPaaS.com Dashboard under Integration Monitoring and the Error Logs.
Validation Rules
Code present: the Business Central shipping method must have a code; the code is the matching key and the source of the iPaaS.com name.
Duplicate matching: before a new iPaaS.com record is created, the integration matches an incoming shipping method to an existing iPaaS.com shipping method by code and links it rather than duplicating.
Testing and Validation
Test Scenarios
Valid shipping method transfer. Transfer a Business Central shipping method with a valid code and name (by polling, Manual Sync, or bulk initialization). Confirm the iPaaS.com shipping method is created with the code as its name and the name as its description.
Duplicate matching. Transfer a shipping method whose code already exists as a shipping method name in iPaaS.com. Confirm the duplicate is detected and the existing iPaaS.com record is linked by external ID rather than a second record being created.
Bulk initialization. Run bulk initialization for Shipping Methods. Confirm all Business Central shipping methods are transferred to iPaaS.com.
Repeat transfer / external ID. Transfer the same shipping method twice. Confirm the second transfer updates the existing iPaaS.com record (matched by code) rather than creating a duplicate.
Missing name. Transfer a shipping method that has a code but no name. Confirm the iPaaS.com record is created with the code as its name and the description left unset.
Validation Checklist
Business Central shipping methods carry a valid, unique code.
Shipping method names are populated in Business Central if the iPaaS.com description should be set.
Web Services are enabled for Shipping Methods in Business Central.
Bulk initialization has been run if an initial data load is required.
Additional Notes
The Business Central code maps to the iPaaS.com name and the Business Central name maps to the iPaaS.com description; these are not one-to-one name matches. Account for this when comparing shipping methods across the two systems.
Custom fields are not supported for the shipping method collection; only the code and name are captured.
Outbound delete is not supported; deleting a shipping method in Business Central does not remove the corresponding iPaaS.com record.
Related Documents
Connections and Settings (pending publication)
Known Limitations (pending publication)