Overview
Customer records can be transferred from iPaaS.com using the Update sync method. This integration allows updates only for customers that already exist in both iPaaS.com and Microsoft Dynamics 365. Any changes made to Customer records in iPaaS.com will be synchronized to Microsoft Dynamics 365 only if the corresponding records are already present.
Before You Begin
Ensure the following prerequisites are in place before configuring this integration.
iPaaS.com Requirements
Customer record must already exist in iPaaS.com
Customer must have valid CustomerNumber, Email, and Address data
Customer must be linked to an existing Microsoft Dynamics 365 customer record
Microsoft Dynamics 365 Requirements
Customer record must already exist in Microsoft Dynamics 365
Web Services must be enabled for Customers, Customer Card, Contact Card, and Customer Price Group
Valid codes must exist for: TaxAreaCode, GenBusPostingGroup, CustomerPostingGroup, CustomerPriceGroup, PaymentTermsCode
ID Format
When manually transferring a Customer from iPaaS.com, use the internal ID as the Customer identifier. This ID uniquely represents each Customer record within iPaaS.com.
Example: 153237
Mapping Collection Status
Status: Enabled
Trigger Events: Customer Update
Supported Child Collections
This integration does not support any child collections.
System Caveats
iPaaS.com Caveats
Update Only: This mapping collection only processes updates. Customer records must already exist in both systems before synchronization can occur.
Category Handling: iPaaS.com supports multiple category assignments, whereas Dynamics 365 allows only one. The integration selects the first category from the list and assigns it to the Dynamics 365 Customer Price Group field.
Microsoft Dynamics 365 Caveats
CountryRegionCode: Country code must be 10 characters or fewer and must match an existing country code in Microsoft Dynamics 365.
TaxAreaCode: Mappings must provide the exact Code of an eligible Tax Area in Microsoft Dynamics 365.
GenBusPostingGroup Mappings must provide the exact Code of an eligible Gen. Business Posting Group in Microsoft Dynamics 365.
CustomerPostingGroup: Mappings must provide the exact Code of an eligible Customer Posting Group in Microsoft Dynamics 365.
CustomerPriceGroup: Mappings must return the exact Code of an eligible Customer Price Group in Microsoft Dynamics 365.
PaymentTermsCode: Mappings must return the exact Code of an eligible Payment Term in Microsoft Dynamics 365.
Authentication and Security
Microsoft Dynamics 365 API credentials are required for accessing the Customer API. Ensure credentials are stored securely within the iPaaS.com credential manager.
Integration Flow
The integration processes iPaaS.com Customer update records as follows:
Customer record is updated in iPaaS.com.
iPaaS.com validates the customer exists in Microsoft Dynamics 365.
Customer data fields are mapped from iPaaS.com to Microsoft Dynamics 365 format.
Primary billing address fields are extracted using
FieldFromFirstMatch.Category is converted to CustomerPriceGroup code.
Customer record is updated in Microsoft Dynamics 365.
Transfer status and any errors are logged in iPaaS.com.
Mappings
Parent: Microsoft Dynamics 365 Update Customer FROM iPaaS
Description
This mapping collection handles updates to existing Microsoft Dynamics 365 customer records from iPaaS.com. It maps identity fields, contact information, address data, and business posting groups.
Mapping Type | Source (iPaaS.com) | Destination (Dynamics 365) | Description |
Dynamic Formula |
| No | (Required) Preserves the existing Customer Number value from Microsoft Dynamics 365 instead of replacing it. |
Dynamic Formula |
| Name | (Required) Combines FirstName and LastName to create the full customer name. |
Dynamic Formula |
| Address | (Recommended) Extracts Address1 from the primary billing address. |
Dynamic Formula |
| CountryRegionCode | (Recommended) Extracts country code from the primary billing address. Must be 10 characters or fewer. |
Dynamic Formula |
| City | (Recommended) Extracts city from the primary billing address. |
Dynamic Formula |
| County | (Recommended) Extracts region/county from the primary billing address. |
Dynamic Formula |
| PostCode | (Recommended) Extracts postal code from the primary billing address. |
Dynamic Formula |
| PhoneNo | (Recommended) Extracts phone number from the primary billing address. |
Field | EmailAddress | (Required) Maps customer email address. | |
Dynamic Formula |
| CustomerPriceGroup | (Recommended) Converts iPaaS.com categories to Microsoft Dynamics 365 Customer Price Group code. Selects the first category if multiple exist. |
Static | 10 DAYS | PaymentTermsCode | (Required) Sets payment terms. Adjust this value to match your Microsoft Dynamics 365 configuration. |
Error Handling
Invalid Email
Email format is incorrect.
Description: The email field format is invalid.
Resolution: Ensure the email field is valid and follows the format user@example.com.
Missing Email
Email field is empty or null.
Description: The email field cannot be empty or null.
Resolution: Ensure the email field is present in iPaaS.com before syncing.
Invalid Country Code
Country code does not exist in Microsoft Dynamics 365.
Description: The provided country code is not configured in Microsoft Dynamics 365.
Resolution: Ensure the country code is 10 characters or fewer and matches a valid country code in Microsoft Dynamics 365.
Missing Required Static Field
Required field code mapping is missing.
Description: A value provided for a required field code mapping (such as PaymentTermsCode) is missing or not configured in Microsoft Dynamics 365.
Resolution: Verify mapped values (e.g., NONTAX, GENERAL, WHOLESALE, N30) exist in Microsoft Dynamics 365, or adjust the mappings to return appropriate values.
Validation and Testing
Before deploying this integration, verify the following configuration items and run the test scenarios to confirm proper operation.
Validation Checklist
Customer Number is present and unique.
Email is present, valid, and unique.
Customer record exists in both iPaaS.com and Microsoft Dynamics 365.
Country code is 10 characters or fewer and exists in Microsoft Dynamics 365.
All static code values (PaymentTermsCode, etc.) exist in Microsoft Dynamics 365.
Test Scenarios
Scenario 1: Valid Customer Update
Update an existing customer in iPaaS.com. Customer record should be updated in Microsoft Dynamics 365 with all mapped fields.
Scenario 2: Missing Email (Failure Case)
Attempt to update a customer without an email address. Sync should fail with error logged.
Scenario 3: Invalid Country Code (Failure Case)
Attempt to update a customer with an invalid country code. Sync should fail with appropriate error.
Additional Notes
This mapping collection only processes updates; it does not create new customer records.
Customer records must be linked between iPaaS.com and Microsoft Dynamics 365 before updates can sync.
iPaaS.com supports multiple categories, but Microsoft Dynamics 365 only accepts one CustomerPriceGroup; the first category is used.
Adjust static values (PaymentTermsCode, etc.) to match your Microsoft Dynamics 365 configuration.