Overview
Location records can be transferred to iPaaS.com through both manual sync and polling. This integration supports syncing of Location data to iPaaS.com using the Microsoft Dynamics 365 Location ID for identification. Bulk initialization is also supported for initial data migration.
Before You Begin
Ensure the following prerequisites are in place before configuring this integration.
Microsoft Dynamics 365 Requirements
Location records must exist with valid Code and Name data
Web Services must be enabled for Locations
iPaaS.com Requirements
API credentials with create/update permissions for Location API
Custom fields must be created for Dynamics Location data (Contact, AddressLine1, AddressLine2, City, State, Country, PostalCode, PhoneNumber, Email, Website)
Location names must be unique in iPaaS.com
ID Format
When manually transferring a Location to iPaaS.com, use the Microsoft Dynamics 365 internal ID as the Location identifier. This ID uniquely represents each Location record within Microsoft Dynamics 365.
Example: 3f2504e0-4f89-11d3-9a0c-0305e82c3301
Mapping Collection Status
Status: Enabled
Trigger Events: Location Create, Location Update
System Caveats
Microsoft Dynamics 365 Caveats
Code as Fallback Name: If no Name exists for a Location in Microsoft Dynamics 365, the location is created using Code as the Name in iPaaS.com.
iPaaS.com Caveats
Duplicate Name Checking: Duplicate name checking is implemented for this integration. Locations with duplicate names will be rejected.
Custom Fields Required: Several custom fields must be created in iPaaS.com to support extended location data mapping.
Authentication and Security
Microsoft Dynamics 365 API credentials are required for accessing the Location API. Ensure credentials are stored securely within the iPaaS.com credential manager.
Integration Flow
The integration processes Microsoft Dynamics 365 Location records as follows:
Location is created or updated in Microsoft Dynamics 365.
Polling or manual sync triggers the transfer.
iPaaS.com authenticates with the Microsoft Dynamics 365 API.
Location data fields are mapped from Microsoft Dynamics 365 to iPaaS.com format.
Duplicate name checking is performed.
Location record is created or updated in iPaaS.com.
Transfer status and any errors are logged.
Mappings
Parent: Dynamics Add Location To iPaaS
Description
This mapping collection transfers Microsoft Dynamics 365 Locations to iPaaS.com. Duplicate name checking is implemented, and polling is enabled for automatic synchronization. Bulk initialization is also supported for initial data migration.
Mapping Type | Source (Dynamics 365) | Destination (iPaaS.com) | Description |
Field | Contact | Dynamics Location Contact | (Recommended) Maps location contact. |
Field | Address | Dynamics Location AddressLine1 | (Recommended) Maps primary address. |
Field | Address2 | Dynamics Location AddressLine2 | (Recommended) Maps secondary address. |
Field | City | Dynamics Location City | (Recommended) Maps city. |
Field | County | Dynamics Location State | (Recommended) Maps county/state. |
Field | CountryRegionCode | Dynamics Location Country | (Recommended) Maps country code. |
Field | PostCode | Dynamics Location PostalCode | (Recommended) Maps postal code. |
Field | PhoneNo | Dynamics Location PhoneNumber | (Recommended) Maps phone number. |
Field | Dynamics Location Email | (Recommended) Maps email address. | |
Field | HomePage | Dynamics Location Website | (Recommended) Maps homepage/website URL. |
Field | Code | Name | (Required) Maps location code to name. If no Name exists, Code is used. |
Field | Name | Description | (Recommended) Maps location name to description. |
Error Handling
Duplicate Location
Location with this name already exists.
Description: A location with the same name already exists in iPaaS.com.
Resolution: Ensure location names are unique or update the existing record.
Missing Required Field
Code field is empty.
Description: The Code field is required for location creation.
Resolution: Ensure the Location has a valid Code in Microsoft Dynamics 365.
Validation and Testing
Before deploying this integration, verify the following configuration items and run the test scenarios to confirm proper operation.
Validation Rules
Code: Must be present.
Name: Must be unique in iPaaS.com.
Validation Checklist
Location Code is present and valid.
Location name is unique in iPaaS.com.
Custom fields exist in iPaaS.com for extended data.
Test Scenarios
Scenario 1: Valid Location Record
Sync a location from Microsoft Dynamics 365. Location should be successfully transferred to iPaaS.com.
Scenario 2: Duplicate Location (Failure Case)
Attempt to sync a location with a name that already exists. Error should be logged and location rejected.
Scenario 3: Location with All Fields
Sync a location with all address and contact fields populated. All fields should transfer correctly.
Bulk Initialization
After completing the necessary mappings, performing a bulk initialization may be beneficial if location data needs to be integrated initially. To initiate this process, click on the arrow icon next to LOCATION in the iPaaS.com interface. This step triggers the bulk initialization process, ensuring that location records are synchronized within iPaaS.com.
NOTE: This action is only necessary for users who have chosen to integrate locations from Microsoft Dynamics 365. For those not utilizing this feature, bulk initialization is not required and will not have any effect. |
Additional Notes
Duplicate name checking prevents the creation of locations with the same name.
Polling is implemented for automatic synchronization of location changes.
Bulk initialization is available for initial data migration.
If no Name exists in Microsoft Dynamics 365, the Code field is used as the location name in iPaaS.com.
Custom fields must be created in iPaaS.com before syncing extended location data.