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
Important Links
- Pimics in AppSource
- Packages for on-premise (Latest Business Central)
- Packages for on-premise (other versions)
Pimics PIM
Pimics PIM 14.0.3
Release date: 22.09.2026
Bugfixes
| Identification | Title | Release Note Summary |
|---|---|---|
| #17182 | Duplicate entry error when selecting Content Header after Reorganize Publication | Selecting a Content Header after reorganizing a publication no longer causes a duplicate-entry error. |
| #25206 | Inherit DESCRIPTION TEXT when same class defined and extended code differs | Description texts with the same Description Class but different extended text codes are inherited as separate lines. |
| #34244 | Deleted entity on the top level remains in the publication after full reorganize | Full publication reorganization removes deleted top-level entities from the publication, while allowing custom entities to be handled through the extension event. |
| #37535 | Rename Item - double confirmation - Pimics or BC? | Renaming an existing item no longer shows duplicate confirmations or causes an Item does not exist error. |
| #37575 | Product Features: Edit in Excel | Edit in Excel correctly publishes changes made to Product Features. |
| #41317 | "Certification Log contains warning. Do you want to open the log?" when no warnings is shown | Certification no longer reports that the Certification Log contains warnings when no warnings are present. |
| #43779 | Flex Categories: Classes not inherited to children with non-standard parent type | Classes are inherited correctly through flexible category structures when the parent group type is not Item Group. |
| #44099 | Description Text preview FactBox not cleared when text is deleted | The description text preview FactBox is cleared after the selected description text is deleted. |
| #44102 | Description Texts: Show HTML source omits ampersand characters required in HTML encoded entities | Show HTML source preserves ampersands required for correctly encoded HTML entities. |
| #44138 | Group structure worksheet - calculation mismatch on two Catalog Groups | Calculate Group Types reuses the correct top-level Catalog Group and creates the expected assignments in the group structure worksheet. |
| #44179 | Pimics initial setup does not update inheritance | The Pimics initial setup updates inheritance when the action is set to run in the background. |
| #44219 | Flexible categories: No inheritance or correct fields after assigning item | Assigning an item in a flexible category structure fills Parent Group Type and Parent Group Code correctly and applies product feature inheritance. |
| #44280 | Allow Delete Used Documents | Users with Allow Delete Used Documents enabled can delete used documents through the intended confirmation and cleanup process. |
| #44305 | Allow Code Duplicity across master entities via catalog setup | A new Allow Code Duplicity In Allocations setting lets you allow duplicate codes across master entities when your setup requires it. |
| #44324 | Cross Reference deletion - No dialog when already inherited on children | Deleting a cross-reference shows the configured inheritance confirmation when inherited child records are affected. |
| #44330 | Catalog Group -> Inherit from Cross Reference | Features can be inherited from a referenced Catalog Group when the cross-reference type allows inheritance. |
| #44351 | Publication Entity is expanded regardless the setup of parent PUG for cross reference types | Publication expansion respects the Expanding Type configured for publication groups used with cross-reference types. |
| #44414 | UpdateCustomData not covered for publication update | Custom data is updated for custom entities during publication updates, not only during reorganization. |
| #44434 | Flexible Categories - assignment from allocation line doesn't set Parent Group Type | Assigning an entity from an allocation line in flexible categories sets Parent Group Type correctly. |
Pimics PIM 14.0.2
Release date: 10.09.2026
Bugfixes
| Identification | Title | Release Note Summary |
|---|---|---|
| #31490 | Validate Publication Structure Type for Sana on the Publication Card | You can no longer set up a Sana publication with the unsupported Single Item Group publication structure type; this is now validated directly on the Publication Header and Publication Channel. |
| #34244 | Deleted entity on the top level remains in the publication after full reorganize | A full publication reorganization now removes deleted top-level master-data entities from the publication instead of leaving obsolete lines in the structure. |
| #37574 | Publication Group: Include Feature values is not used | The Include Feature Values field on Publication Group has been marked as obsolete and is no longer visible on the card. |
| #40150 | Product Feature, add column Value Set Description | The Product Feature list can now show an optional Value Set Description column, making it easier to identify which value set a feature uses. |
| #40880 | Number field of Product Feature does not link to class | The Number field on a Product Feature line now links to the Class table when the line references a class, matching the existing links for Feature and Feature Group. |
| #41180 | API Translation - Overtakes 1st translation line for Item description Pimics finds, if language is not specified | API Translation now checks that a language code is set on the Publication Header instead of always using the first translation line found when no language is specified. |
| #41571 | Repository actions fail if document repository differs from default repository | Actions such as Move to Default Repository, Refresh Metadata, and Refresh Thumbnail now work correctly when a document's repository differs from the default repository setup. |
| #43198 | SharePoint - function allowing to select specific file and provide it | You can look up and select a specific file from a SharePoint site, library, and folder directly, instead of only browsing folder contents. |
| #43443 | Align Code Duplicity checking for Product Feature Element and Inherit Path | The duplicate-code check for Product Feature Element and Inheritance Path no longer raises an error when only viewing structure (for example, the Allocation Tree or FactBoxes); it now applies only when inheritance of the product feature itself is evaluated. |
| #43512 | Translation CZ | The Czech localization has been updated with the latest Pimics PIM text changes for this release. |
| #43514 | Translation FR | The French localization files have been synchronized with the latest Pimics PIM text changes for this release. |
| #43797 | Catalog Group still referenced in Standard Catalog Group after deletion | Deleting a Catalog Group now clears the Standard Catalog Group reference on its child categories, preventing invalid references from remaining after deletion. |
| #43802 | Item delete blocked by certification update | Deleting a certified item with Product Features no longer fails because deleting the features triggers a certification update that blocked the item delete. |
| #43921 | Gallery action "Set as main picture" doesn't trigger change in "Picture Document ID" | Using Set as main picture in the picture gallery now correctly updates the Picture Document ID on the parent record. |
| #43922 | Gallery action "Set as main picture" is not enabled | The Set as main picture gallery action is now enabled for all non-main pictures after adding multiple pictures at once. |
| #43923 | Text deletion - Inherit set as delete, but choice dialog is shown | Deleting a Description Text now respects the Inherit Delete = Delete setting in Catalog Setup instead of still asking you to choose between stop, keep, or delete. |
| #43928 | Description Text deletion on Item raises choice dialog for deletion - copy/delete | Deleting a Description Text on an item no longer shows an unnecessary copy/delete choice dialog when there are no related records to consider. |
| #43955 | Feature Value Type is not correctly filled on Publication Line | The Feature Value Type on a Publication Line is now correctly set to Range Numeric for features of that type, instead of Number. |
| #43964 | Cross refference delete error | Deleting a Cross-Reference no longer triggers an unnecessary copy/delete confirmation dialog when the entity has no inheritance set up. |
| #44039 | Bulk Edit Items no longer in Pimics Base | The Bulk Edit Items action is available again without requiring the Pimics Beta application area. |
| #44093 | Original decision Overtake/Delete is not respected for Classes, Documents, Description Texts | When deleting master data with inherited classes, documents, and description texts, Pimics now reuses the deletion choice you already made instead of asking the same inherited-data question again for each data type. |
| #44107 | Allow page action "Reorganize Publication Line" for custom entities | Custom publication line types, such as Picture Group, can now be included in the Reorganize Publication Line action through a new integration event, instead of being limited to standard entities. |
| #44139 | Allocation Line - can't add different Line Type once already one is set | You can now change the Line Type of an existing allocation line instead of it staying locked to the type used on the first line. |
| #44149 | Pre-Translate not working for Item Descriptions | Pre-Translate for item descriptions now runs correctly instead of the dialog closing without applying any translation. |
| #44187 | Picture not found | Fixed a Picture Document has not been found error that could occur when linking entities in an allocation structure due to an incorrect Picture Document ID reference. |
| #44225 | Standart catalog group stays when deleted | Deleting a catalog group now also clears related standard allocation links, so obsolete standard allocation data does not remain on the chapter. |
| #44242 | 'Record "XML Buffer" temporary' does not contain a definition for 'GetAttributeValue' | Translation import now reads XLIFF language and state attributes through the supported XML Buffer method, avoiding failures caused by the previous attribute call. |
Pimics PIM 14.0.1
Release date: 28.08.2026
Bugfixes
| Identification | Title | Release Note Summary |
|---|---|---|
| #40153 | Allocation Tree doesn't show newly added top-level elements | Newly added top-level entities now appear immediately in the Allocation Tree without requiring the page to be reopened. |
| #40158 | Allocation Tree does not always show main picture | The Allocation Tree now consistently displays the main picture for the selected entity. |
| #40950 | Pimics Users: Create Self does not recognize delegate admin | Create Self now correctly recognizes delegate administrators. |
| #41336 | Description title not updated when changing Description Class | Changing the Description Class now updates the Description Title when the title has not been manually changed. |
| #41998 | Rule action convert units: parameter selection appends to existing value without separator | Selecting To Feature ID values in the Convert Units rule action now replaces the previous selection instead of appending to it. |
| #42904 | Value ID is not assigned when entering numeric/boolean feature values manually | Manually entering a numeric or boolean feature value that matches a predefined value now assigns the corresponding Value ID. |
| #43724 | FeatureMatrix: Button 'Product Features' throws error | The Product Features action on the Feature Matrix now opens correctly without a Type can't be empty error. |
| #43729 | Error because of outdated record when saving picture order | Saving a changed picture order no longer fails because of an outdated catalog document record. |
| #43766 | Parent Group Type and Code not cleared when clearing standard group field | Clearing a standard group now also clears Parent Group Type and Parent Group Code. |
| #43780 | Value is always created for numeric, date and logical features | Numeric, date, and logical feature values are no longer created automatically when no matching predefined value exists, preventing unnecessary PIMX Value records. |
| #43824 | Rule list/card cannot be opened anymore when Update Field parameter "Type" is empty, but "Field No." is set | Rule lists and cards can now be opened when an Update Field action has a field number but no type selected. |
| #43840 | 'The record is not open' when opening Bulk Edit Cross-References from page search | Bulk Edit Cross-References is no longer available from page search without the required source record, preventing a The record is not open error. |
| #43881 | Error when reorganizing items with existing publication price line without currency code | Reorganizing items with legacy publication price lines that have no currency code no longer fails when the local currency is assigned. |
| #43893 | Error when switching publication rule type to Hide Empty Group | You can switch a publication rule to Hide Empty Group without receiving a dictionary error from leftover rule parameters. |
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
| Identification | Title | Release Note Summary |
|---|---|---|
| #43257 | Custom Line Types are not handled using "Edit Publication Tree" | Edit Publication Tree now correctly handles publication lines with custom line types, including their lookup and custom-data processing. |
| #43563 | Empty nodes | Sana category responses no longer contain empty Node elements when a category line is skipped. |
| #43617 | Item delete error : update from certification (by delete allocation) | Deleting a certified item with a parent Item Group no longer causes an outdated-record error when related allocation lines are removed. |
| #43637 | Document inheritance | Document inheritance now correctly supports category relationships, including enabling and disabling inheritance and resetting the inherited state for catalog documents. |
| #43639 | Perfomance of assisted setup when overtaking data from BC | Assisted setup performance is improved when existing data is overtaken from Business Central. |
| #43725 | Channel GET when publication header channel empty | Publication reorganization now handles a publication header with an empty channel when preparing channel data. |
BMECat for Pimics 14.0
Release date: 21.09.2026
New and updated features
| Identification | Title | Release Note Summary |
|---|---|---|
| #15008 | Export BMECat using interfaces | BMECat 2005 export now prepares XML fragments during publication reorganization and assembles them into the final file during publishing. The updated process is easier to extend and supports product data such as prices, features, keywords, descriptions, pictures, documents, and catalog structures. |
| #41275 | Import BMECat file from SharePoint | You can select a BMECat file from SharePoint in the import wizard instead of uploading it from the local computer. This supports centralized handling of large supplier catalogs; the feature is available under the Beta application area while larger-file scenarios are validated. |
Bugfixes
| Identification | Title | Release Note Summary |
|---|---|---|
| #39434 | Documents, Features, Keywords, Texts are not in the file | BMECat 2005 publishing now includes related documents, features, keywords, and texts inside the correct product element. The export uses publication-line GUID relationships to associate related lines with their parent product and writes the publication-line export consistently as UTF-8. |
| #39507 | MIME_INFO Element Placement in PRODUCT Structure | BMECat product XML now follows the required schema sequence for product details, features, and MIME information, preventing XSD validation errors caused by incorrectly ordered elements. |
| #39509 | xmlns | The BMECat namespace is now applied to the document root without adding unwanted namespace declarations to nested product elements. |
| #39734 | Price is required | BMECat product output now provides the required price structure when no calculated price is available and places price details in the schema-required position. |
| #44320 | File or SharePoint | The BMECat import wizard now distinguishes between selecting a local file and selecting a file from SharePoint through the Source field. |
Vendor Catalog
Vendor Catalog 14.0.1
Release date: 17.09.2026
Bugfixes
| Identification | Title | Release Note Summary |
|---|---|---|
| #44325 | Vendor Item |
Vendor Catalog imports no longer fail when a vendor provides a unit of measure longer than 10 characters. The full unit text is preserved, and the unit code is left empty when no matching unit can be found. |
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.2 |
| 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.