Table of Contents

Release notes: Pimics 14

Content

Other versions: Pimics 13, Pimics 12, Pimics 11, Pimics 10, Pimics 9, Pimics 8 Integrations: Pimics add-on in Sana Commerce

Pimics PIM

Pimics PIM 14.0

Release date: 24.08.2026

New and updated features

Identification Title Release Note Summary
#8197 Copy publication You can copy an entire publication either into a new target publication or into an existing one without lines, instead of rebuilding structures manually. This update improves publication target selection and number-series handling, reducing setup effort for repeated publication variants while keeping channel configuration consistent.
#14694 DeepL - Ignore Tags, Using Glossary You can prevent selected product terms from being translated by using ignore-tag handling and support glossary-driven translation confirmation workflows. This update helps preserve product names in multilingual text and improves translation quality for long descriptions.
#24674 Set picture order easily You can reorder pictures in a dedicated UI workflow based on drag-and-drop style interaction instead of maintaining order values manually. The requested implementation uses a temporary working dataset and writes sequential order values back to Business Central after confirmation, including support for entity-specific column layouts and follow-up usability improvements.
#30403 Deleting of master data in Pimics You get a more structured deletion concept for Pimics master entities, focused on balancing user-friendly cleanup with dependency protection and clear user feedback. It adds safer handling for entities with related features, texts, pictures, and references so deletion is more predictable in complex data structures.
#31256 Issues with Synchronize Features to Attributes and consistency Feature-to-attribute synchronization is aligned to be more consistent, including linked translation synchronization behavior for attributes and attribute values. Synchronization now covers translation updates when sync settings change and when source feature/value translations are created, updated, or deleted, reducing long-term data drift between Pimics features and BC attributes.
#31794 Update Pimics' number series' "Last Used No." according to the existing objects You can update Pimics number-series state from existing records when migration or manual corrections bypass standard insert logic and leave Last Used No. inconsistent. A dedicated Catalog Setup action evaluates configured series and updates sequence continuity to prevent collisions when new records are created after imports or corrections.
#34898 E-Class Import E-Class import is improved to better support real datasets and practical usage. This includes hierarchy-constraint adjustments, identifier and search behavior for classification IDs, and validation for cloud and supplier-catalog scenarios so imported structures can be used reliably in operational processes.
#37628 Exchange PIM Pictures with Variants Variant-picture handling is extended for BC28 capabilities, including controlled overtake of media and synchronization between Pimics catalog documents and Item Variant thumbnail behavior. It also improves main-picture assignment and compatibility handling for variant-specific visual differentiation.
#38581 Mapping of Features Feature mapping introduces a mapped-value concept where Pimics feature values can be derived from fields on Item, Variant, or Catalog Item records instead of manual entry. It also improves source-of-truth behavior, fallback logic, and extensibility to keep mapped values synchronized while reducing repetitive maintenance effort on large assortments.
#40762 RegEx replacement support for rule action and import transformation RegEx processing is expanded from simple match extraction to full replacement scenarios for rule actions and import transformations. The specification adds a replacement parameter, scoped match behavior, whole-input replacement control, and upgrade-safe defaults so existing configurations remain stable while enabling advanced cleanup and normalization use cases in vendor-catalog and transformation pipelines.
#41553 Inheritance from Catalog Groups Inheritance behavior is extended for Catalog Group relationships, including Catalog Group to Catalog Group and Catalog Group to Chapter scenarios with texts, features, pictures, and related data. The defined scope includes page controls, alignment with default setup, and explicit prevention of circular inheritance loops to make inheritance usable in broader production structures.
#41631 Cross Reference entities with related data in API API behavior is adjusted so cross-reference entities can be consumed together with relevant related data in the beta/2.1 model without circular expansion problems. The update removes restrictive source filters, adds reference-type context to items/categories endpoints, and extends references with structural context fields to simplify integration.
#41685 Sana Commerce: Handle deleted data Deleted data handling for Sana integration is formalized across items, cross-references, media, and category-related outputs so update-index responses remain complete after removals. Publication-line change tracking is used to propagate affected-item updates and reduce stale storefront content when data is deleted or detached in Pimics.
#41866 Option to enable/disable Sana web service log You can control request/response logging for Sana web services to reduce high activity-log volume and disk consumption in large environments. The implemented scope introduces a setup flag in publication setup context for message logging decisions while preserving error logging, giving administrators operational control between diagnostics depth and runtime overhead.
#41906 Worksheets > Export Description Text: Export Text Translations with filter on Translation Type and Language Export Description Text now supports translation-focused filtering by adding filters for language and translation type. Base description text remains part of the export while translation selection becomes controllable, improving precision of multilingual export payloads for external processing.
#42066 Default inheritance and translate setup on existing items/nostock items after Pimics install Post-install setup now addresses existing items and non-stock items more explicitly, because default Catalog Setup flags alone do not retroactively apply to historical records. Assisted setup steps now support translation and inheritance initialization so customers can prepare existing datasets consistently after installation.

Bugfixes

Vendor Catalog

Vendor Catalog 14.0

Release date: 24.08.2026

New and updated features

Identification Title Release Note Summary
#40762 RegEx replacement support for rule action and import transformation RegEx transformation in Vendor Catalog now supports both classic match extraction and configurable replacement logic. You can define a replacement template with group references, choose whether replacement is applied to a selected match only or reflected in the whole input text, and keep existing mappings stable because default parameters preserve previous behavior.

Bugfixes

Identification Title Release Note Summary
#43449 Vendore item changes activation status despite error Activation flow in codeunit PIMX Item Activation now raises dedicated integration events before Integration Status is set to Activated, so extension logic can run and fail before the status transition is persisted. This prevents inconsistent states where activation status was changed although downstream processing still failed.
#42481 Excel Mapping Line: Assist Edit button has no effect The non-functional AssistEdit behavior on the Excel mapping line UI was removed, and users now use the existing lookup behavior for Destination Relation Filter without a misleading extra action state.
#43012 Destination relation settings (PIMX Filter) and transformation parameters not deleted when deleting import mapping Cleanup on mapping deletion was extended across Excel and XML mapping structures so related PIMX Filter and import-transformation parameter records are removed together with parent mapping records, preventing orphaned configuration data after deletes.
#43013 Mapping From Excel creates invalid destination relation settings after first matching feature column Mapping creation from Excel now limits relation-filter creation to valid feature-mapping cases and avoids carrying invalid mapping context to subsequent columns. Import processing was aligned to apply relation filters only for matching table context, reducing invalid field-target combinations during import execution.
#41007 Import Excel Import Mapping: Invalid Destination Table No. Excel mapping import/export handling was corrected so destination-table context is preserved during mapping transport. This prevents imported mappings from ending with table number 0 and eliminates downstream destination-field lookup failures.

Pimics AI

Pimics AI 14.0

Release date: 26.08.2026

New and updated features

Identification Title Release Note Summary
#41428, #43507 Generate Image Alt Description Text Pimics AI now provides a consolidated alternative-description workflow for pictures that supports accessible e-commerce content, so visitors who are blind can understand what a picture shows through meaningful alternative text. It combines earlier concept validation with productized implementation in Pimics365. You can generate descriptions from picture context using a dedicated proposal dialog, apply them in single or multi-record flows, and manage approval with explicit confirmation actions. Configuration support was added for default description class and deployment selection to make rollout predictable across environments.

Bugfixes

Identification Title Release Note Summary
#37795 Pimics demo: AI Feature proposal startIndex ('-1') must be a non-negative value. (Parameter 'startIndex') Actual value was -1. Feature-value suggestion error handling was hardened in PIMX AI Feature Proposal and PIMX Azure OpenAI Wrapper. The fix validates and normalizes malformed AI XML responses before parsing, adds clearer invalid-response errors, and enforces safer Azure OpenAI resource-type usage for on-premise and managed/custom scenarios through setup validation and runtime checks.
#38202 The XML node with the name 'Number' could not be found. Feature-value parsing was aligned to a strict XML contract in PIMX AI Feature Proposal and PIMX AI Prompts. The prompt now requires <Root><Features><Feature ... /></Features></Root>, and parser logic validates /Root/Features/Feature nodes and mandatory Number attributes before writing values, preventing failures caused by inconsistent AI response structures.

Latest supported versions per BC

The latest Pimics supports the 3 latest versions of Business Central. If you have an older version, the table below helps you identify what the latest released version is.

BC Version Latest Supported Version Latest Released Version (Pimics PIM)
28 16 14.0.0
27 15 13.1.7
26 14 12.1
25 13.1.7 13.1.7
24 12 12.1
23 11 10.1
22 10 9.2
21 - 10.0

Latest supported version is the version for which we are willing to perform a downgrade for BC under the valid license. The downgrade process is available upon request and must be scheduled; the version is ready in approximately 2 weeks. Latest Released Version is a version that is the newest for that version of BC (Pimics PIM extension). It is available right now for installation without any necessary steps.

See Also