Overview
Customer records from iPaaS.com can be transferred to Microsoft Dynamics 365 through manual synchronization or webhooks. When customer/created or customer/updated webhooks are subscribed to in iPaaS.com, any new or updated customer records are automatically sent to Microsoft Dynamics 365.
Before You Begin
Ensure the following prerequisites are in place before configuring this integration.
iPaaS.com Requirements
Customer records must have valid CustomerNumber, Name, Email, and Address data
Categories must be configured if CustomerPriceGroup mapping is required
Webhooks must be configured for automatic synchronization
Microsoft Dynamics 365 Requirements
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
Country codes must be configured and match iPaaS.com country values
Web Services must be customized to accept custom fields if needed
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 Create
Supported Child Collections
This integration does not support any child collections.
System Caveats
iPaaS.com Caveats
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
Customer Number Length: The customer number in Microsoft Dynamics 365 is limited to a maximum of 20 characters.
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.
Custom Fields Support
Microsoft Dynamics 365 supports extended fields for integration to add additional custom fields. This extension supports Customer models.
Adding Custom Fields for Customer FROM iPaaS.com
NOTE: In Microsoft Dynamics 365, customize the Web Services to accept the desired custom field in the customer request. Contact your MiSP for assistance customizing Microsoft Dynamics 365 Web Services. |
In Microsoft Dynamics 365, create a custom field in iPaaS.com Subscription.
In iPaaS.com, create a custom field in Microsoft Dynamics 365 Subscription.
In iPaaS.com, map the custom field to a static or dynamic data source.
Ensure the data flows correctly from iPaaS.com to Microsoft Dynamics 365.
Validate that the field values are updated appropriately.
Setup Requirements
Microsoft Dynamics 365 Configuration
Web Services must be enabled for Customers, Customer Card, Contact Card, and Customer Price Group.
Customize Web Services to accept custom fields if required.
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 records as follows:
Customer is created or updated in iPaaS.com.
Webhooks automatically trigger the transfer of the customer from iPaaS.com to Microsoft Dynamics 365.
iPaaS.com authenticates with the Microsoft Dynamics 365 API.
Customer Number is truncated to 19 characters if needed (max 20 characters in Dynamics 365).
Name is constructed from FirstName and LastName.
Primary billing address fields are extracted using
FieldFromFirstMatch.Categories are converted to CustomerPriceGroup code.
Customer record is created in Microsoft Dynamics 365.
Transfer status and any errors are logged in iPaaS.com.
Mappings
Parent: Microsoft Dynamics 365 Add Customer FROM iPaaS.com
Description
This mapping collection handles the creation of 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) Truncates customer number to max 19 characters (Dynamics 365 limit is 20). |
Dynamic Formula |
| Name | (Required) Combines FirstName and LastName to create 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. | |
Static | ATLANTA, GA | TaxAreaCode | (Required) Sets tax area code. Adjust to match your Dynamics 365 configuration. |
Static | DOMESTIC | GenBusPostingGroup | (Required) Sets Gen. Business Posting Group. Adjust to match your configuration. |
Static | DOMESTIC | CustomerPostingGroup | (Required) Sets Customer Posting Group. Adjust to match your configuration. |
Dynamic Formula |
| CustomerPriceGroup | (Recommended) Converts iPaaS.com categories to Microsoft Dynamics 365 Customer Price Group code. |
Static | 10 DAYS | PaymentTermsCode | (Required) Sets payment terms. Adjust to match your 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., ATLANTA GA, DOMESTIC, 10 DAYS) 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.
Country code is 10 characters or fewer and exists in Microsoft Dynamics 365.
All static code values exist in Microsoft Dynamics 365.
Customer Number is 20 characters or fewer.
Test Scenarios
Scenario 1: Valid Customer Record
Sync a new customer from iPaaS.com. The customer should be successfully transferred to Microsoft Dynamics 365.
Scenario 2: Missing Email (Failure Case)
Attempt to sync a customer without an email address. Sync should fail with an error logged.
Scenario 3: Invalid Country Code (Failure Case)
Attempt to sync a customer with an invalid country code. Sync should fail with an appropriate error.
Additional Notes
If the iPaaS.com Customer ID matches the Microsoft Dynamics 365 Customer Number, the records are automatically linked through record matching. In this case, no error is generated and the transfer is not rejected.
Customer number is automatically truncated to 19 characters to comply with Microsoft Dynamics 365's 20-character limit.
iPaaS.com supports multiple categories, but Microsoft Dynamics 365 only accepts one CustomerPriceGroup; the first category is used.
Adjust static values (TaxAreaCode, GenBusPostingGroup, CustomerPostingGroup, PaymentTermsCode) to match your Microsoft Dynamics 365 configuration.