Overview
Customer Company records from iPaaS.com can be transferred to Microsoft Dynamics 365 through manual synchronization or webhooks. This integration enables syncing of customer company data from iPaaS.com to Microsoft Dynamics 365 using the Company API.
Before You Begin
Ensure the following prerequisites are in place before configuring this integration.
iPaaS.com Requirements
Company records must have valid Name, Email, and Address data
Company must have a valid internal ID for identification
Categories must be configured if CustomerPriceGroup mapping is required
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
ID Format
When manually transferring a Customer Company from iPaaS.com, use the internal ID as the Company identifier. This ID uniquely represents each Customer Company record within iPaaS.com.
Example: 1532
Mapping Collection Status
Status: Enabled
Trigger Events: Company Create, Company Update
Supported Child Collections
This integration does not support any child collections.
System Caveats
iPaaS.com Caveats
Template Mappings: Mappings for company create operations are provided with template mappings; however, mappings for update operations must be configured manually according to your business requirements.
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.
Custom Fields Support
Microsoft Dynamics 365 supports extended fields for integration to add additional custom fields. This extension supports Company models.
Adding Custom Fields for Company FROM iPaaS.com
NOTE: In Microsoft Dynamics 365, customize the Web Services to accept the desired custom field in the company request. Contact your MiSP for assistance customizing Microsoft Dynamics 365 Web Services. |
In Microsoft Dynamics 365, create a custom field in the 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.
Ensure all required posting group codes exist.
Authentication and Security
Microsoft Dynamics 365 API credentials are required for accessing the Company API. Ensure credentials are stored securely within the iPaaS.com credential manager.
Integration Flow
The integration processes iPaaS.com Company records as follows:
Company is created or updated in iPaaS.com.
Webhook automatically triggers the transfer of company from iPaaS.com to Microsoft Dynamics 365.
iPaaS.com authenticates with the Microsoft Dynamics 365 API.
Company data fields are mapped from iPaaS.com to the Microsoft Dynamics 365 format.
Primary billing address fields are extracted using FieldFromFirstMatch.
Categories are converted to CustomerPriceGroup code.
Company record is created or updated in Microsoft Dynamics 365.
Transfer status and any errors are logged in iPaaS.com.
Mappings
Parent: Microsoft Dynamics 365 Company Add FROM iPaaS.com
Description
This mapping collection handles the creation and update of Microsoft Dynamics 365 company records from iPaaS.com. It maps company identity fields, contact information, address data, and business posting groups.
Mapping Type | Source (iPaaS.com) | Destination (Dynamics 365) | Description |
Dynamic Formula |
| No | (Required) Maps the iPaaS.com Company ID to the Microsoft Dynamics 365 Company Number. |
Field | Name | Name | (Required) Maps the company 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 |
| Post_Code | (Recommended) Extracts postal code from the primary billing address. |
Dynamic Formula |
| Phone_No | (Recommended) Extracts phone number from the primary billing address. |
Field | EmailAddress | E_Mail | (Required) Maps company email address. |
Static | NONTAX | TaxAreaCode | (Required) Sets tax area code. Must match an eligible Tax Area in Microsoft Dynamics 365. |
Static | GENERAL | GenBusPostingGroup | (Required) Sets Gen. Business Posting Group. Must match an eligible code in Microsoft Dynamics 365. |
Static | WHOLESALE | CustomerPostingGroup | (Required) Sets Customer Posting Group. Must match an eligible code in Microsoft Dynamics 365. |
Dynamic Formula |
| CustomerPriceGroup | (Recommended) Converts iPaaS.com categories to Microsoft Dynamics 365 Customer Price Group code. |
Static | N30 | PaymentTermsCode | (Required) Sets payment terms. Must match an eligible Payment Term in Microsoft Dynamics 365. |
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.
Invalid Company Number
CompanyNumber already exists in Microsoft Dynamics 365.
Description: A company with the same number already exists.
Resolution: Ensure CompanyNumber values are unique before transfer.
Missing Required 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 Rules
Email: Must be unique and properly formatted.
CompanyNumber: Must be present and unique.
Validation Checklist
Customer Company Number is present and unique.
Email is present, valid, and unique.
Category mapping returns valid CustomerPriceGroup code.
All static code values exist in Microsoft Dynamics 365.
Test Scenarios
Scenario 1: Valid Company Record
Sync a new company from iPaaS.com. Company should be successfully transferred to Microsoft Dynamics 365.
Scenario 2: Missing Email (Failure Case)
Attempt to sync a company without an email address. Sync should fail with error logged.
Scenario 3: Successful Price Group Mapping
Sync a company with valid categories. CustomerPriceGroup should be successfully assigned.
Additional Notes
If the iPaaS.com Company ID matches the Microsoft Dynamics 365 Company Number, the records are automatically linked through record matching. In this case, no error is generated, and the transfer is not rejected.
Adjust static values (TaxAreaCode, GenBusPostingGroup, CustomerPostingGroup, PaymentTermsCode) to match your Microsoft Dynamics 365 configuration.
Template mappings are provided for create operations; update mappings must be configured manually.