--- title: "29th October 2026" slug: "29th-october-2026" updated: 2026-10-30T13:56:21Z published: 2026-10-30T13:56:21Z canonical: "pccdocs.bluemeteor.com/29th-october-2026" --- > ## Documentation Index > Fetch the complete documentation index at: https://pccdocs.bluemeteor.com/llms.txt > Use this file to discover all available pages before exploring further. # 29th October 2026 ### ![Two glowing star shapes on a gradient background, creating a vibrant visual effect.](https://cdn.document360.io/a899ba09-fd60-4d47-8b32-aabf7b60a39a/Images/Documentation/ChatGPT Image Aug 14, 2025, 07_12_51 PM.png?sv=2026-02-06&spr=https&st=2026-10-31T11%3A01%3A31Z&se=2026-10-31T12%3A01%3A31Z&sr=c&sp=r&sig=H1TI80LA7oOIMqFSHeKlf6BRjStWI8mqXT%2BlDuF5mLk%3D) List of Features | **No.** | **Feature** | **Description** | | --- | --- | --- | | 1. | Added support for splitting attribute values and UoM into separate target attributes in SOP | Added the “Split source attribute value and UoM to multiple target attributes” rule on the Field Transformation screen during template creation in SOP. Users can assign separate target attributes for the source value and its Unit of Measure (UoM). For example, a source value of “250 G” can populate separate weight and UoM attributes as “250” and “G”. Users can also map source units to the target attribute’s List of Values (LoV). The rule supports both default mappings and conditional overrides. Users must configure value and UoM targets before saving. When the source contains a value without a UoM, only the value target is populated. With this enhancement, users can separate combined measurement data during onboarding without manually preparing separate source attributes in SOP. | | 2. | Added support for splitting a source attribute into multiple target attributes in SOP | Added the “Split source attribute value to multiple target attributes” rule on the Field Transformation screen during template creation in SOP. Users can extract portions of a source attribute using standard or custom delimiters, or by specifying character positions and extraction lengths. Each target attribute can have its own extraction configuration, including the extraction direction and delimiter occurrence. Users can apply additional string operations to each extracted portion, including adding or removing text, finding and replacing text, and changing the text case. A preview displays the extracted values and the results of the configured operations. With this enhancement, users can separate combined product information into individual catalog attributes and format each extracted value during onboarding in SOP. | | 3. | Added support for combining multiple source attributes into a single target attribute in SOP | Added the “Multiple attributes to single” rule on the Field Transformation screen during template creation in SOP. Users can select multiple source attributes, arrange their order, and configure standard or custom separators and patterns to build a single target attribute. Users can also include the associated UoM for source attributes that have UoM information. Reordering source attributes retains the configured separators. Blank source values are omitted without introducing unnecessary separators, and the target attribute remains empty when all selected source values are blank. With this enhancement, users can combine information such as brand, model, and color into consistently formatted product titles or descriptions during onboarding in SOP. | | 4. | Added support for scheduled import of product data from Infor Cloud into PCC | Added support for scheduled imports of product data from Infor Cloud into PCC. The integration processes taxonomy, product, warehouse, and configured product relationship data in sequence, skipping stages with no data. Products are classified using part-number matches in the configured catalog. Products without a matching category, or with multiple matching categories, are assigned to the default category. Products with multiple matching categories are identified in the notification for review. With this enhancement, users can import Infor Cloud data through an automated workflow with no manual intervention in PCC. | ### ![Two glowing star shapes on a gradient background, creating a vibrant visual effect.](https://cdn.document360.io/a899ba09-fd60-4d47-8b32-aabf7b60a39a/Images/Documentation/ChatGPT Image Aug 14, 2025, 07_12_51 PM.png?sv=2026-02-06&spr=https&st=2026-10-31T11%3A01%3A31Z&se=2026-10-31T12%3A01%3A31Z&sr=c&sp=r&sig=H1TI80LA7oOIMqFSHeKlf6BRjStWI8mqXT%2BlDuF5mLk%3D) List of Improvements | **No.** | **Improvement** | **Description** | | --- | --- | --- | | 1. | Enhanced attribute selection and validation for 1WorldSync exports in PCC | Enhanced the 1WorldSync export process to include dimension attributes, such as height, width, and weight, according to the EACH or CASE option selected in the “Exporting Data For” field on the New Export pop-up. Attributes associated with the unselected entity are excluded, while other required attributes continue to follow the existing export rules. If required dimension attributes are missing for the selected entity, the affected SKU fails validation and is not exported. An error identifies the missing information. With this enhancement, users can export dimension data for the selected entity and identify missing required attributes before the affected SKUs are exported to 1WorldSync in PCC. | | 2. | Updated Grainger template attributes and validation in PCC | Added 11 attributes to the Grainger template, with data types, help text, and required-field validation configured according to the updated attribute specifications. Updated the allowed values for the Low Lead Compliance Code attribute to reflect the revised Grainger requirements. These changes apply to both the template and API. With this enhancement, users can provide the additional product information and validate data against the updated Grainger requirements when preparing SKUs for syndication in PCC. | ### ![](https://cdn.document360.io/a899ba09-fd60-4d47-8b32-aabf7b60a39a/Images/Documentation/image(232).png?sv=2026-02-06&spr=https&st=2026-10-31T11%3A01%3A31Z&se=2026-10-31T12%3A01%3A31Z&sr=c&sp=r&sig=H1TI80LA7oOIMqFSHeKlf6BRjStWI8mqXT%2BlDuF5mLk%3D) List of Bug Fixes | **No.** | **Module** | **Problem Summary** | **Resolution** | | --- | --- | --- | --- | | 1. | SOP | Historical supplier mappings could remain unchanged after a distributor modified and finalized mappings. As a result, supplier mappings could retain previously populated selections instead of reflecting the distributor’s updates. | Updated mapping finalization to apply the distributor’s selections when AI mapping finalization choice is set to DISTRIBUTOR. When AI mapping finalization choice is set to BOTH, the distributor’s updates replace historical prefills while preserving mappings explicitly selected by the supplier. Attributes that the distributor has not mapped retain their existing supplier mappings. | | 2. | PCC | Duplicate fields appeared in the field mapping list when users edited a Shopify Direct Connector configuration and clicked Next on the Field Mapping screen. | Resolved an issue where clicking Next on the Field Mapping screen created duplicate field entries when users edited a Shopify Direct Connector configuration. |