Overview
Customer records can be transferred to iPaaS.com through both manual sync and polling. This integration supports syncing of Customer data to iPaaS.com using the Microsoft Dynamics 365 Customer ID for identification.
Before You Begin
Ensure the following prerequisites are in place before configuring this integration.
Microsoft Dynamics 365 Requirements
Customer records must exist with valid Name and Email data
Web Services must be enabled for Customers, Customer Card, Contact Card, and Customer Price Group
Customer must be of Type "Person" and RecordType "Customer"
iPaaS.com Requirements
API credentials with create/update permissions for Customer API
Email addresses must be unique in iPaaS.com
ID Format
When manually transferring a Customer to iPaaS.com, use the Microsoft Dynamics 365 internal ID as the Customer identifier. This ID uniquely represents each Customer record within Microsoft Dynamics 365.
Example: 3f2504e0-4f89-11d3-9a0c-0305e82c3301
Mapping Collection Status
Status: Enabled
Trigger Events: Customer Create, Customer Update
Supported Child Collections
Parent Collection: Dynamics Add Customer TO iPaaS
Child Collection 1: Dynamics Add Customer Address TO iPaaS
System Caveats
Microsoft Dynamics 365 Caveats
Type and RecordType Filtering: Only records where Type is "Person" and RecordType is "Customer" are processed.
iPaaS.com Caveats
Email Matching: Before adding a new customer to iPaaS.com, the system checks whether there is already a customer record by matching the email address.
Email Uniqueness: Customer email addresses must be unique. Duplicate emails will cause sync failures.
Setup Requirements
Microsoft Dynamics 365 Configuration
Web Services must be enabled for Customers, Customer Card, Contact Card, and Customer Price Group.
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 Microsoft Dynamics 365 Customer records as follows:
Customer is created or updated in Microsoft Dynamics 365.
Polling or manual sync triggers the transfer.
Mapping filter validates the customer (Type == "Person" && RecordType == "Customer").
iPaaS.com checks for existing customer by email address matching.
iPaaS.com authenticates with Microsoft Dynamics 365 API.
Customer data fields are mapped from Microsoft Dynamics 365 to iPaaS.com format.
Child collection processes customer addresses.
Customer record is created or updated in iPaaS.com.
Transfer status and any errors are logged.
Mappings
Parent: Dynamics Add/Update Customer TO iPaaS
Mapping Filter
Type == "Person" && RecordType == "Customer"
Description
This filter ensures only Customer records are processed. Records must have Type "Person" and RecordType "Customer".
Mapping Type | Source (Dynamics 365) | Destination (iPaaS.com) | Description |
Field | No | CustomerNumber | (Required) Maps Dynamics 365 customer number. |
Field | Name | FirstName | (Required) Maps customer name to FirstName. |
Field | EmailAddress | (Required) Maps customer email address. |
Child Collection: Dynamics Add Customer Address TO iPaaS
Mapping Filter
SourceTypeName != "ParentOnly"
Description
This filter processes address records except those marked as ParentOnly. Prevents duplicate addresses from being added.
Mapping Type | Source (Dynamics 365) | Destination (iPaaS.com) | Description |
Static | true | PreventDuplicate | Prevents duplicate addresses from being added to iPaaS.com. |
Field | Address | Address1 | Maps primary street address. |
Field | City | City | Maps city. |
Field | County | Region | Maps county/region. |
Field | CountryRegionCode | Country | Maps country code. |
Field | PostCode | PostalCode | Maps postal code. |
Field | PhoneNo | PhoneNumber | Maps phone number. |
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 Microsoft Dynamics 365 before syncing.
Duplicate CustomerNumber
CustomerNumber already exists in iPaaS.com.
Description: A customer with the same CustomerNumber already exists.
Resolution: Ensure CustomerNumber values are unique or update the existing record.
Validation and Testing
Before deploying this integration, verify the following configuration items and run the test scenarios to confirm proper operation.
Validation Rules
EmailAddress: Must be valid email format.
CustomerNumber: Must be unique.
Validation Checklist
Customer Number is present and unique.
Email is present, valid, and unique.
Customer Type and RecordType are correct.
Test Scenarios
Scenario 1: Valid Customer Record
Sync a customer from Microsoft Dynamics 365. Customer should be successfully transferred to iPaaS.com.
Scenario 2: Duplicate CustomerNumber (Failure Case)
Attempt to sync a customer with an existing CustomerNumber. Error should be logged and customer rejected.
Scenario 3: Missing Email (Failure Case)
Attempt to sync a customer without an email address. Sync should fail with error logged.
Scenario 4: Customer with Address
Sync a customer with address data. Customer and address should be created in iPaaS.com.
Additional Notes
Before adding a new customer, the system checks for existing records by matching email addresses.
Both polling and manual sync are supported for this integration.
Address duplicate prevention is enabled by default.
Webhooks trigger automatic transfers between iPaaS.com and Microsoft Dynamics 365.