Magento Product Category from iPaaS

Mapping Type

Source (iPaaS.com)

Destination (Magento)

Description

Dynamic Formula

SharedCatalogIds (custom field)

SharedCatalogIds (custom field)

This mapping is essential for assigning a single product category to multiple Shared Catalogs, thereby establishing a one-to-many relationship. It utilizes a record-level custom field named "SharedCatalogIds", whose value is assigned to a subscription-level custom field with the same name. This value represents the iPaaS product category IDs, separated by commas (,). These IDs are later used in the handle prerequisite step to validate whether each ID corresponds to a valid iPaaS product category. During this validation, the system checks whether the referenced category has the custom field IsSharedCatalog. If the field is missing or explicitly set to false, the category is created as a shared catalog from prerequisite. This transfer is created using the shared catalog mapping collection rather than the current mapping, ensuring that the category is assigned to the appropriate, predefined Shared Catalogs later during create/update of category.

Dynamic Formula

var external = await GetExternalIdAsync(ParentId, "Product Category", SpaceportSystemId); return COALESCE(external, "2");

ParentId

Field

Name

Name

Static

true

IsActive

Dynamic Formula

CoalesceToInt(GetCustomFieldValue(CustomFields, "Sort Order"), 0)

Position

Dynamic Formula

var sharedCatalogIds = GetCustomFieldValue(CustomFields, "Shared Catalog Ids"); if(!string.IsNullOrWhiteSpace(sharedCatalogIds)){ return await GetStoreIdByName("B2B Store View"); } return null;

StoreId_Catalog

This mapping is essential/required for assigning a single product category to multiple Shared Catalogs, establishing a one-to-many relationship. The provided formula utilizes the store name to retrieve its corresponding store ID. If a valid store name is provided, the function returns the appropriate store ID. However, if an invalid or unrecognized store name is supplied, the function defaults to returning 0, which corresponds to the Admin (default) store view in Magento. It's important to note that in Magento, store ID 0 represents the Admin store view, which serves as the default context for global data. Assigning categories to Shared Catalogs under store ID 0 may lead to unexpected behavior, since Shared Catalogs are typically tied to specific websites or store views. Therefore, to ensure accurate assignment of categories to the intended Shared Catalogs, it's crucial to provide valid and existing store names. Alternatively, if stricter validation is preferred, an exception can be raised when the returned store ID is 0, as the commented code in the mapping formula suggests. This approach prevents assignments to unintended store views by ensuring the presence of a valid store mapping before proceeding. Use either approach depending on your business requirements and error-handling preferences. If this functionality is not required, you may remove this mapping to prevent any unintended assignments. For more information on Magento's store architecture and Shared Catalogs, you can refer to the following resources: Shared Catalog Overview | Adobe Commerce - Experience LeagueMagento 2 Shared Catalog Guide - Firebear Studio These resources provide comprehensive insights into managing Shared Catalogs and understanding Magento's store hierarchy.

Note: Even if the shared catalog mapping collection specifies a different store at the mapping level, and this mapping itself has a different store configured, the assignment will not be affected. Categories will still be assigned across the specified shared catalogs as expected.