Overview
Product records from iPaaS.com can be transferred to Microsoft Dynamics 365 through manual synchronization or webhooks. When product/created or product/updated webhooks are subscribed to in iPaaS.com, any new or updated product 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
Product records must have valid Sku, Description, and required field data
Catalog_Item_Group should be configured if mapping is required
TaxClass must be configured for tax group mapping
Microsoft Dynamics 365 Requirements
Web Services must be enabled for Items and Item Card
Valid posting group codes must exist (GenProdPostingGroup, InventoryPostingGroup)
Base Unit of Measure must be configured
ID Format
When manually transferring a Product from iPaaS.com, use the internal ID as the product identifier. This ID uniquely represents each product record within iPaaS.com.
Example: ITEM1001
Mapping Collection Status
Status: Enabled
Trigger Events: Product Create, Product Update
Supported Child Collections
This integration does not support any child collections.
System Caveats
iPaaS.com Caveats
Description Length: The Description field is truncated to 99 characters to comply with Microsoft Dynamics 365 field length limits.
Microsoft Dynamics 365 Caveats
Item Type: Products are created with Type "Inventory" by default.
Base Unit of Measure: Products use "EA" (Each) as the default base unit of measure.
Posting Group: GenProdPostingGroup and InventoryPostingGroup must be configured with valid codes.
Authentication and Security
Microsoft Dynamics 365 API credentials are required for accessing the Item API. Ensure credentials are stored securely within the iPaaS.com credential manager.
Integration Flow
The integration processes iPaaS.com Product records as follows:
Product is created or updated in iPaaS.com.
Webhooks or manual sync triggers the transfer.
iPaaS.com authenticates with Microsoft Dynamics 365 API.
Description is truncated to 99 characters if needed.
Product data fields are mapped from iPaaS.com to Microsoft Dynamics 365 format.
Product record is created or updated in Microsoft Dynamics 365.
Transfer status and any errors are logged in iPaaS.com.
Mappings
Parent: Dynamics Add Product FROM iPaaS
Description
This mapping collection handles the creation and update of Microsoft Dynamics 365 item records from iPaaS.com products.
Mapping Type | Source (iPaaS.com) | Destination (Dynamics 365) | Description |
Field | Catalog_Item_Group | CatItemGroup | (Recommended) Maps catalog item group. |
Field | Sku | No | (Required) Maps product SKU to item number. |
Dynamic Formula |
| Description | (Recommended) Truncates description to 99 characters maximum. |
Static | Inventory | Type | (Required) Sets item type to Inventory. |
Static | EA | BaseUnitOfMeasure | (Required) Sets base unit of measure to Each. |
Field | Weight | NetWeight | (Recommended) Maps product weight. |
Static | GENERAL | GenProdPostingGroup | (Required) Sets Gen. Product Posting Group. Adjust to match your configuration. |
Field | TaxClass | TaxGroupCode | (Recommended) Maps tax class to tax group code. |
Static | GENERAL | InventoryPostingGroup | (Required) Sets Inventory Posting Group. Adjust to match your configuration. |
Field | DefaultPrice | UnitPrice | (Recommended) Maps default price to unit price. |
Static | Tracking Only | OrderTrackingPolicy | (Recommended) Sets order tracking policy. |
Error Handling
Duplicate SKU
Item with this SKU already exists.
Description: A product with the same SKU already exists in Microsoft Dynamics 365.
Resolution: Ensure SKU values are unique or update the existing record.
Invalid Posting Group
Posting group code not found.
Description: The specified posting group code does not exist in Microsoft Dynamics 365.
Resolution: Verify that GenProdPostingGroup and InventoryPostingGroup codes exist in Microsoft Dynamics 365.
Missing Required Field
SKU field is empty.
Description: The SKU field is required for product creation.
Resolution: Ensure the product has a valid SKU in iPaaS.com before syncing.
Validation and Testing
Before deploying this integration, verify the following configuration items and run the test scenarios to confirm proper operation.
Validation Rules
ProductId: Must exist in iPaaS.com and correspond to a valid record.
Type: Must be statically set to a supported product type.
Validation Checklist
ProductId exists and is valid.
SKU is present and unique.
Type field is mapped correctly.
Posting group codes exist in Microsoft Dynamics 365.
Test Scenarios
Scenario 1: Valid Product
Sync a new product from iPaaS.com. Product should be successfully created in Microsoft Dynamics 365.
Scenario 2: Long Description
Sync a product with description longer than 99 characters. Description should be truncated without error.
Scenario 3: Duplicate SKU (Failure Case)
Attempt to sync a product with an existing SKU. Appropriate error handling should occur.
Additional Notes
Description is automatically truncated to 99 characters to comply with Microsoft Dynamics 365 limits.
Adjust static values (GenProdPostingGroup, InventoryPostingGroup, BaseUnitOfMeasure) to match your Microsoft Dynamics 365 configuration.
Products are created with Type "Inventory" by default; adjust for service items if needed.
Both manual sync and webhooks are supported for this integration.