Overview
Magento Product Category Assignment can be transferred from iPaaS.com using an Add/Update sync method. This mapping supports the automated synchronization of Product Category Assignment records from iPaaS into Magento via the Product Category Assignment API.
Mapping Collection Status
Mapping Status: Enabled.
Trigger Events: The sync is triggered by the creation or update of Product Category Assignment in Magento.
ID Format: When manually syncing, the Product Category Assignment ID from iPaaS is used.
Conflicting Mappings: This mapping applies only to Product Category Assignment. Ensure no other mappings target the same Magento entity to prevent data from being overwritten.
System Caveats
Magento Caveats
Magento requires a valid SKU and CategoryId for successful category assignment.
Invalid or non-existing SKUs in Magento will cause the record to be rejected.
Duplicate product-category assignments are ignored by Magento.
iPaaS.com Caveats
Product and Category data must exist in iPaaS prior to running this mapping.
The system uses dynamic formulas to retrieve external SKUs and category identifiers.
If the SKU or CategoryId cannot be resolved, the mapping will fail for that record.
Setup Requirements
Magento Configuration
Sku: Must already exist in Magento before category assignment is created.
CategoryId: Must refer to a valid Magento category.
iPaaS.com Configuration
Magento2 API Username: Used by iPaaS to access and create category assignments in Magento.
Magento2 API Key: Authenticates iPaaS API requests for secure data transfer.
Authentication & Security
Magento2 API UserName: Used to access iPaaS API for fetching Company and related data.
Magento2 API Key: Used to access iPaaS API for fetching Company and related data.
Integration Flow
Retrieve Data: iPaaS fetches Product and Category mapping records.
Validate Product: Confirms that the product exists in Magento using the SKU reference.
Validate Category: Retrieves and confirms the CategoryId based on the provided category data.
Map Fields: Uses dynamic formulas to link SKU and CategoryId for assignment.
Sync Record: Sends the mapping data to Magento to create the category association.
Confirm Assignment: Magento validates and records the relationship.
Mappings
Parent Collection: Magento Product Category Assignment From iPaaS
Mapping Type | Source (iPaaS.com) | Destination (Magento) |
Dynamic Formula |
| Sku |
Dynamic Formula |
| CategoryId |
Error Handling
Missing SKU
Description: SKU could not be retrieved or resolved from iPaaS.
Resolution: Ensure the ProductId in iPaaS corresponds to a valid SKU in Magento.
Missing or Invalid CategoryId
Description: The CategoryId is missing or refers to a non-existent category in Magento.
Resolution: Validate the category mapping and ensure CategoryId exists in Magento.
Duplicate Category Assignment
Description: The product is already assigned to the specified category in Magento.
Resolution: Duplicates are ignored; no action needed unless reassignment is required.
Validation Rules & Testing
Validation Checklist
SKU exists and is active in Magento.
CategoryId corresponds to a valid Magento category.
API authentication is configured and authorized.
iPaaS dynamic formulas return valid identifiers.
Test Scenarios
Sync a valid product-category record: Verify category successfully appears in Magento under the correct product.
Attempt sync with invalid ProductId: Confirm error “Missing SKU.”
Attempt sync with invalid CategoryId: Confirm error “Missing or Invalid CategoryId.”
Resync existing association: Verify duplicate handling (no duplicate created).
Additional Notes
This flow supports Add and delete.