Overview
Product Category records can be transferred to iPaaS.com through both manual sync and polling. This integration supports syncing of Product Category data to iPaaS.com using the Microsoft Dynamics 365 Category Code for identification.
Before You Begin
Ensure the following prerequisites are in place before configuring this integration.
Microsoft Dynamics 365 Requirements
Item Category records must exist with a valid Code and Description
Web Services must be enabled for Item Categories
iPaaS.com Requirements
API credentials with create/update permissions for Product Category API
Parent category lookup must be configured for hierarchical categories
ID Format
When manually transferring a Microsoft Dynamics 365 Category to iPaaS.com, use the Category Code as the Product Category identifier. Enter the correct Category Code into the EXTERNAL ID input field on the iPaaS.com manual sync page.
Example: FURN
Mapping Collection Status
Status: Enabled
Trigger Events: Product Category Create, Product Category Update
Supported Child Collections
This integration does not support any child collections.
System Caveats
Microsoft Dynamics 365 Caveats
Code Filtering: Categories are filtered based on Code patterns. Categories starting with "01-80", "02-80", or with Description "N/A", or without a hyphen in the Code are excluded.
iPaaS.com Caveats
Parent Category Resolution: Parent categories are resolved using a Lookup Translation table for Category Code Translation.
Authentication and Security
Microsoft Dynamics 365 API credentials are required for accessing the Item Category API. Ensure credentials are stored securely within the iPaaS.com credential manager.
Integration Flow
The integration processes Microsoft Dynamics 365 Item Category records as follows:
Item Category is created or updated in Microsoft Dynamics 365.
Polling or manual sync triggers the transfer.
Mapping filter validates the category (excludes specific code patterns).
iPaaS.com authenticates with the Microsoft Dynamics 365 API.
Category data is mapped to the iPaaS.com Product Category format.
Parent category is resolved via Lookup Translation.
Product Category record is created or updated in iPaaS.com.
Transfer status and any errors are logged.
Mappings
Parent: Dynamics Add Product Category TO iPaaS
Mapping Filter
if (Code.StartsWith("01-80") || Code.StartsWith("02-80") || Description == "N/A" || !Code.Contains("-")) {
return false;
}
return true;
Description
This filter excludes categories with specific code patterns:
Codes starting with "01-80" or "02-80"
Categories with Description "N/A"
Codes without a hyphen character
Field Mappings
Mapping Type | Source (Dynamics 365) | Destination (iPaaS.com) | Description |
Field | Code | ERP_Category_ID | Maps the MSD365 Code to the ERP_Category_ID custom field. |
Field | Description | Name | Maps the Description to the Name. |
Error Handling
Duplicate Category Code
Category with this code already exists.
Description: A Product Category with the same Code already exists in iPaaS.com.
Resolution: Ensure Category codes are unique or update the existing record instead of creating a new one.
Missing Required Field
Code field is empty.
Description: The Code field is required for Product Category creation.
Resolution: Ensure the Item Category has a valid Code in Microsoft Dynamics 365.
Parent Category Not Found
Parent category not found in lookup translation.
Description: The parent category reference cannot be resolved.
Resolution: Ensure the Category Code Translation lookup table 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
Code: Must be present, contain a hyphen, and not match excluded patterns.
Description: Should be present and not "N/A".
Validation Checklist
Category Code is present and valid.
Code contains a hyphen character.
Code does not start with "01-80" or "02-80".
Description is not "N/A".
Category Code Translation lookup is configured for parent resolution.
Test Scenarios
Scenario 1: Valid Category Record
Sync a Product Category from Microsoft Dynamics 365. Category should be created in iPaaS.com with correct parent relationship.
Scenario 2: Excluded Code Pattern (Filtered)
Attempt to sync a category with code starting with "01-80". Category should be filtered and not transferred.
Scenario 3: Category with Parent
Sync a category with a valid parent reference. Parent relationship should be established in iPaaS.com.
Scenario 4: Category Without Hyphen (Filtered)
Attempt to sync a category with code "MISC" (no hyphen). Category should be filtered and not transferred.
Additional Notes
Categories with specific code patterns are filtered out by the mapping filter.
Parent-child relationships are established using the Category Code Translation lookup table.
Both polling and manual sync are supported for this integration.
The Code field serves as the unique identifier for matching records between systems.