Overview
When a Shipping Method is created or updated in Microsoft Dynamics 365 Business Central, the corresponding shipping method record is created or updated in iPaaS.com. This mapping collection transfers the shipping method code and description. The system automatically retrieves and registers all Shipping Method records using their internal identifiers, ensuring accurate and complete synchronization.
Shipping Method records can be transferred to iPaaS.com through initialization, polling, and manual sync.
Before You Begin
Ensure the following prerequisites are in place before configuring this integration.
MS Dynamics 365 Requirements
Web Services must be enabled for Shipping Methods
Shipping Method records must have a valid Code and Name
iPaaS.com Requirements
Duplicate shipping method name checking is enabled for this integration — shipping method names must be unique in iPaaS.com
ID Format
When performing a manual transfer of a Shipping Method from MS Dynamics 365, use the internal ID as the shipping method identifier.
This ID uniquely represents each Shipping Method record within Business Central and ensures the correct data is transferred to iPaaS.com.
Example:
2000000054
Mapping Collection Status
Status: Enabled
Trigger Events: Create, Update
Supported Child Collections
This mapping collection has no child collections.
Data Requirements
Mandatory Fields
Name (mapped from Code)
Description (mapped from Name)
System Caveats
iPaaS.com Caveats
Duplicate Name Checking: Duplicate name checking is implemented for this integration. If a shipping method with the same name already exists in iPaaS.com, the record will not be created as a duplicate.
Integration Caveats
Field Name Mapping: Note that the Business Central "Code" field maps to the iPaaS.com "Name" field, and the Business Central "Name" field maps to the iPaaS.com "Description" field. These are not one-to-one name matches.
Authentication and Security
MS Dynamics 365 Business Central uses OAuth 2.0 authentication to authorize API requests during transfer operations. Ensure credentials are stored securely within the iPaaS.com credential manager.
Integration Flow
The integration processes MS Dynamics 365 Shipping Method records as follows:
Shipping Method is created or updated in Business Central.
Polling detects the change, or a manual sync/bulk initialization is triggered.
iPaaS.com authenticates with Business Central using OAuth 2.0.
The shipping method Code is mapped to the iPaaS.com Name field.
The shipping method Name is mapped to the iPaaS.com Description field.
Duplicate name checking validates that the shipping method does not already exist in iPaaS.com.
The shipping method record is created or updated in iPaaS.com.
Transfer status and any errors are logged in iPaaS.com.
Bulk Initialization
After completing the necessary mappings, performing a bulk initialization may be beneficial if Shipping Method data needs to be integrated. To initiate this process, click the arrow icon next to SHIPPING METHOD in the iPaaS.com subscription settings. This triggers the bulk initialization process, synchronizing all Shipping Method records to iPaaS.com.
Bulk initialization is only required for users who have chosen to integrate Shipping Methods. For those not utilizing this feature, bulk initialization is not necessary and will have no effect.
Mappings
Parent: Shipping Method Add To iPaaS.com
Description
This mapping collection transfers Shipping Method records from Microsoft Dynamics 365 Business Central to iPaaS.com. It maps the shipping method code as the name and the shipping method name as the description. Duplicate name checking prevents creation of duplicate records in iPaaS.com.
Mapping Type | Source (MSD 365) | Destination (iPaaS.com) | Description |
Field | Code | Name | Maps the Business Central shipping method code as the shipping method name in iPaaS.com. |
Field | Name | Description | Maps the Business Central shipping method name as the description in iPaaS.com. |
Error Handling
Duplicate Shipping Method Name
Shipping method name already exists in iPaaS.com.
Description: A shipping method with the same name (mapped from Code) already exists in iPaaS.com.
Resolution: Review the existing shipping method in iPaaS.com. If the record should be updated rather than created, ensure the external ID is correctly linked between Business Central and iPaaS.com.
Validation and Testing
Validation Rules
Shipping method names must be unique in iPaaS.com. The integration checks for duplicates before creating new records.
Both Code and Name must be populated in Business Central for the mapping to succeed.
Validation Checklist
Shipping Method records in Business Central have valid Code and Name values.
Web Services are enabled for Shipping Methods in Business Central.
No duplicate shipping method names exist in iPaaS.com (or duplicates are resolved before sync).
Bulk initialization has been run if an initial data load is required.
Test Scenarios
Scenario 1: Valid Shipping Method Sync
Sync a Shipping Method from Business Central with a valid Code and Name. Verify the record is created in iPaaS.com with Code mapped to Name and Name mapped to Description.
Scenario 2: Duplicate Shipping Method
Sync a Shipping Method where the Code already exists as a shipping method Name in iPaaS.com. Verify that the duplicate is detected and handled appropriately.
Scenario 3: Bulk Initialization
Run bulk initialization for Shipping Methods. Verify all Shipping Method records from Business Central are synchronized to iPaaS.com.
Additional Notes
The Business Central "Code" maps to iPaaS.com "Name" and "Name" maps to iPaaS.com "Description". These are not one-to-one name matches.
Duplicate name checking is active for this integration.
Polling, initialization, and manual sync are all supported transfer methods.
Bulk initialization only needs to be run once during initial setup or when a full resync is required.