Overview
Products from Microsoft Dynamics 365 can be transferred to iPaaS.com using either manual synchronization or polling. This integration supports both simple product data and inventory, enabling the creation and update of product records in iPaaS.com to ensure consistent and accurate information across systems.
Before You Begin
Ensure the following prerequisites are in place before configuring this integration.
Microsoft Dynamics 365 Requirements
Product records must exist with valid Item Number and Description
Web Services must be enabled for Customer Price Groups, Item Card, Items, and Item Categories
Sales Prices must be configured if Customer Price Group transfer is required
Locations must be configured for inventory transfer
iPaaS.com Requirements
API credentials with create/update permissions for Product API
Custom fields must be created for sales code data mapping
Location linking must be established for inventory transfer
ID Format
When performing manual transfers of Microsoft Dynamics 365 Simple Products to iPaaS.com, input the correct identifier in the iPaaS.com field on the manual sync page.
For Simple Products, use the Simple Product ID:
Example: 6fbc9163-0295-ef11-8a6d-6045bdc8dfe6
Mapping Collection Status
Status: Enabled
Trigger Events: Product Create, Product Update
Supported Child Collections
Parent Collection: Dynamics Add Product TO iPaaS
Child Collection: Dynamics Add Product Inventory Add TO iPaaS
System Caveats
Microsoft Dynamics 365 Caveats
Sales Price Configuration: Sales prices must be configured with appropriate sales codes for Customer Price Group mapping.
Location Code Required: Inventory transfers are only supported for locations defined with a code. Unspecified locations will not be transferred as iPaaS.com inventory records.
iPaaS.com Caveats
Product Type Translation: Microsoft Dynamics 365 product types are translated to iPaaS.com types (e.g., Inventory → Physical, Service → Service Items).
Custom Fields for Sales Prices: Custom fields must be created in iPaaS.com to store formatted sales price data from multiple sales codes.
Setup Requirements
Microsoft Dynamics 365 Configuration
Web Services must be enabled for Customer Price Groups, Item Card, Items, and Item Categories.
Authentication and Security
Microsoft Dynamics 365 API credentials are required for accessing the Items API. Ensure credentials are stored securely within the iPaaS.com credential manager.
Integration Flow
The integration processes Microsoft Dynamics 365 Product records as follows:
The product is created or updated in Microsoft Dynamics 365.
Polling or manual sync triggers the transfer.
iPaaS.com authenticates with the Microsoft Dynamics 365 API.
Product data fields are mapped from Microsoft Dynamics 365 to iPaaS.com format.
Product type is translated using lookup translation.
Sales prices are formatted using preset configurations.
Child collection processes inventory data per location.
The product record is created or updated in iPaaS.com.
Transfer status and any errors are logged.
Mappings
Parent: Dynamics Add/Update Product TO iPaaS
Description
This mapping collection transfers Microsoft Dynamics 365 products to iPaaS.com, including sales price data and product attributes.
Mapping Type | Source (Dynamics 365) | Destination (iPaaS.com) | Description |
Field |
| testpro | (Recommended) Formats sales prices for WALKIN sales code. |
Field |
| test | (Recommended) Formats sales prices for RETAIL sales code. |
Field |
| Sales Code A1141DN Data (MSD) | (Recommended) Formats sales prices for A1141DN sales code. |
Field | No | Sku | (Required) Maps item number to SKU. |
Field | Description | Description | (Recommended) Maps product description. |
Lookup Translation | See Lookup Table, | Type | (Required) Translates Dynamics 365 product type to iPaaS.com type (e.g., Inventory → Physical, Service → Service Items). |
Field | UnitPrice | DefaultPrice | (Recommended) Maps unit price to default price. |
Field | No | Name | (Required) Maps item number to product name. |
Static | Active | Status | (Required) Sets product status to Active. |
Field | TaxGroupCode | TaxClass | (Recommended) Maps tax group code to tax class. |
Field | NetWeight | Weight | (Recommended) Maps net weight. |
Static | Product | TrackingMethod | (Required) Sets tracking method to Product. |
Lookup Translation Table
Source (Microsoft Dynamics 365 | Destination (iPaaS.com |
Non-Inventory | Non-Inventory Items |
Service | Service Items |
Inventory | Physical |
Child Collection: Dynamics Add/Update Product Inventory TO iPaaS
Description
Inventory transfers are only supported for locations defined with a code. Unspecified locations will not be transferred as iPaaS.com inventory records.
Type | Source (Dynamics 365) | Destination (iPaaS.com) | Description |
Dynamic Formula |
| Dynamics Cost | (Recommended) Maps unit cost from parent product. |
Dynamic Formula |
| LocationId | (Required) Converts Location Code to Dynamics 365 Location ID, then to iPaaS.com Location ID. |
Field | RemainingQuantity | QtyAvailable | (Required) Maps remaining quantity to available quantity. |
Field | RemainingQuantity | QtyOnHand | (Required) Maps remaining quantity to on-hand quantity. |
Presets for Sales Price
The following presets are important for configuring the product transfer flow:
Transfer Customer Price Groups
A flag that determines whether to transfer Customer Pricing Group (CPG) information. Select True to transfer the data, or False to skip.
Exclude Expired Rules
A flag that determines whether expired sales price rules (based on EndingDate) should be excluded from the transfer. Select True to exclude expired rules and transfer only active pricing data, or False to include all pricing rules.
Sales Codes For Customer Price Groups
A comma-separated list of sales codes to identify customer groups for which custom pricing information should be transferred.
Example: Y1004N, W1035N
Sales Price Field Separator
A string character (such as //, |, or ~) used to separate individual fields within a single sales price record when the pricing data is formatted.
Sales Price Record Delimiter
A single character (such as |, ;, or ~) used to separate multiple sales price records in the formatted output.
Error Handling
Invalid Sales Code
Sales code not found.
Description: The specified sales code does not exist in the sales prices data.
Resolution: Verify that the sales code exists in Microsoft Dynamics 365 and is included in the Sales Codes preset.
Missing Location Code
Location code is empty or invalid.
Description: Inventory record has no location code or invalid location reference.
Resolution: Ensure inventory locations have valid codes defined. Unspecified locations will be skipped.
Product Type Translation Failed
Unknown product type.
Description: The product type cannot be translated using the lookup translation.
Resolution: Verify that the Dynamics Product Status To iPaaS.com lookup translation contains the appropriate mappings.
Validation and Testing
Before deploying this integration, verify the following configuration items and run the test scenarios to confirm proper operation.
Validation Rules
Location ID: Must be mapped and valid in Microsoft Dynamics 365 (for inventory).
Validation Checklist
Product Type is valid and translates correctly.
ProductId exists and is valid.
Sales Code data is relevant and configured.
Location codes are valid for inventory transfer.
Test Scenarios
Scenario 1: Valid Product
Product is successfully transferred with inventory data.
Scenario 2: Invalid Sales Code (Failure Case)
Attempt to format sales prices with invalid code. Error should be logged.
Scenario 3: Missing Location Code
Inventory record without a location code. The inventory record should be skipped.
Scenario 4: Product Type Translation
Products with type "Inventory" should translate to "Physical" in iPaaS.com.
Additional Notes
Product type translation uses the "Dynamics Product Status To iPaaS.com" lookup translation table.
Sales price data is formatted based on preset configurations.
Inventory is only transferred for locations with defined codes.
Custom fields must be created in iPaaS.com for sales code data storage.
Both polling and manual sync are supported for this integration.