What is new in Pimics PIM 14.0
Publication & Export
Copy publication
Business Value
You can create a new publication by copying an existing publication structure instead of rebuilding it manually. This reduces setup time in projects where multiple channels share a similar publication model and helps teams standardize rollout.
This feature focuses on controlled source and target handling, including creation of a new target publication or filling an existing empty one. For users, this means fewer manual steps and lower risk of configuration inconsistency between channels.
Where to start
- Select Search (Alt+Q), enter Publications, and choose the related link.
- Open an existing publication that is closest to the channel setup you need.
- Identify the Copy publication action and run it for one sample target publication.
- Review the copied structure and adjust only the parts that should differ for the new channel.
Technical Changes
The feature is implemented by the PIMX Copy Publication codeunit (70113969), started from the Copy Publication action on the Publication Card and Publication List. The action opens the temporary PIMX Copy Publication Config. table through the PIMX Copy Publication Config. dialog page (70113826), then passes the confirmed configuration to the codeunit.
The process supports copying a complete publication or copying an entity with its descendant publication lines. A new target publication can be created automatically from the configured number series, or an existing target can be selected. Entity copies can be placed at the top level or below a compatible target line. The copy assigns new line identifiers and rebuilds the publication hierarchy so the copied structure remains usable.
Exchange PIM Pictures with Variants
Business Value
You can manage variant-specific imagery in a way that aligns Pimics data with newer Business Central variant-picture capabilities. This improves product presentation quality for assortments where variants differ visually and need distinct thumbnails.
This feature also targets synchronization scenarios where main picture changes must be reflected consistently. For business users, this reduces manual correction cycles and keeps variant media behavior predictable across publication and channel outputs.
Where to start
- Select Search (Alt+Q), enter Pimics Configuration Wizard, and choose the related link.
- In the data-overwrite step, select Pictures and Media and complete the wizard.
- Open an item variant and review its assigned picture in Catalog Documents.
- Change the Main Picture assignment and verify that the item variant picture is updated.
Technical Changes
The PIMX Configuration Wizard can overtake variant pictures from Business Central into Pimics. Pictures are stored as Pimics documents, assigned to the item, and linked to the item variant through Catalog Documents. The first picture is marked as Main Picture.
For Business Central 28 and later, the selected Pimics variant picture is copied to the Item Variant picture and refreshed when the Main Picture assignment changes.
Translation & Texts
DeepL - Ignore Tags
Business Value
You can protect product names and other controlled terms from being translated while still using DeepL for the rest of the text. This improves translation quality in multilingual catalogs where specific words must remain unchanged.
Where to start
- Select Search (Alt+Q), enter HTML Editor or your translation worksheet page, and choose the related link.
- Open a description that contains a product name or another term that must not be translated.
- Mark the protected content with the HTML
translate="no"attribute. - Run the DeepL translation and verify that the marked content remains unchanged.
Technical Changes
DeepL translation uses HTML handling and respects the standard translate="no" attribute. In the HTML editor, protected text is stored in a <span translate="no"> element so product names and other selected content remain unchanged.
DeepL - Using Glossary
Business Value
You can save approved translations in a DeepL glossary and reuse consistent wording in future translations. This reduces repeated corrections for product terms and other controlled language.
Where to start
PRECONDITIONS
Configure DeepL authentication in Catalog Setup and create the glossary in DeepL before you configure it in Pimics.
- Select Search (Alt+Q), enter Translation Glossary List, and choose the related link.
- Create a glossary record, select DeepL as the Translation API Type, and use the Glossary ID lookup to select the DeepL glossary.
- Mark the glossary as Default if it should be used when no glossary is selected on a translation line.
- Select Search (Alt+Q), enter Catalog Translations, and choose the related link.
- Select the glossary for the translation lines, run the translation, and choose Confirm and upload to glossary for approved translations.
Technical Changes
The PIMX Translation Glossary table and Translation Glossary List page store the DeepL glossary configuration. The Glossary ID lookup reads available glossaries from the configured DeepL account, while Default selects the provider's default glossary.
The selected glossary is passed to DeepL during pre-translation. Approved translations can be uploaded with Confirm and upload to glossary, and the glossary code is stored on the translation line.
Worksheets > Export Description Text: Export Text Translations with filter on Translation Type and Language
Business Value
You can export description-text translations with more precise control by filtering on translation language and translation type instead of exporting broad datasets and filtering outside Pimics. This improves handoff quality for localization and publication workflows.
The update also preserves base description text in the output while applying targeted translation filters. For users, this enables cleaner process outputs with less post-processing in Excel or external tooling.
Where to start
- Select Search (Alt+Q), enter Export Description Text, and choose the related link.
- Open the export request and identify filter fields for translation language and translation type.
- Set filters for one target language and one translation type.
- Run the export and verify that base text and selected translations are included as expected.
Technical Changes
The implementation scope specifies extension of request-page filtering behavior for translation data (PIMX Description Text Transl.) while keeping base text export behavior intact.
Master Data
Set picture order easily
Business Value
You can reorder pictures in a dedicated process that is easier to use than editing order values manually on individual rows. This is especially useful for entities with many pictures, where manual maintenance is slow and error-prone.
Where to start
- Select Search (Alt+Q), enter PIM Items, and choose the related link.
- Open an existing item where you already maintain multiple pictures.
- In the item actions, run Pictures, then choose Set Display Order.
- Move pictures into the desired sequence, save, and verify the final order back on the item card.
Technical Changes
Task-linked implementation evidence confirms delivery through new document-order UI components and page integration. Verified AL/BC objects include PIMX DocumentOrderAddIn, PIMX Catalog Picture Order, and PIMX DAM Functions.
Deleting of master data in Pimics
Business Value
You can use a more consistent deletion process for Pimics master data where dependency handling and user feedback are clearer. This reduces operational risk when removing entities that can hold connected data such as features, texts, media, and cross-references.
You can decide what happens to inherited data when the main line is deleted. You can keep related data by copying it to the lower level, or delete it together with the inherited data. This extends the previous product-feature behavior to other related data such as descriptions, references, documents, and classes.
Where to start
- Select Search (Alt+Q), enter the master-data page you maintain (for example Item Group, Product Group, or Chapter), and choose the related link.
- Open an existing record that is no longer needed.
- Identify the delete action and review any warnings about related data.
- Confirm deletion only after checking dependencies, then verify the cleanup result.
Technical Changes
Verified changed objects include the PIMX Master Data Management codeunit, category/entity tables such as PIMX Catalog Group, PIMX Chapter, PIMX Item Group, and PIMX Product Group, and allocation/content tables such as PIMX Allocation Line and PIMX Product Content.
Additional verified changes include the PIMX Class table, PIMX Class Card page, PIMX Feature, PIMX Feature Group, PIMX Feature Group Line, and PIMX Value tables, and cleanup-related handling in the PIMX Product Feature Insert codeunit. Together, these indicate broad lifecycle hardening rather than a single-point delete patch.
The Inherit Delete setting controls how inherited descriptions, references, documents, classes, and product features are handled when a main line is deleted. Pimics can ask the user to Copy to current level or Delete the inherited data, or apply the configured choice automatically.
Update Pimics' number series' "Last Used No." according to the existing objects
Business Value
You can realign number-series state with existing records after migrations or manual corrections that bypass standard insertion logic. This helps prevent duplicate numbering and continuity problems when users continue normal operations.
From a process perspective, this feature supports controlled repair of numbering baselines in environments with historical data imports, reducing the need for repeated manual troubleshooting of numbering collisions.
Where to start
PRECONDITIONS
You should have setup permissions and confirm number-series definitions before updating last used numbers.
- Select Search (Alt+Q), enter Pimics Setup (or number-series setup), and choose the related link.
- Open the maintenance action for updating Pimics number series from existing records.
- Run the action in a controlled window and review the suggested updates.
- Validate one affected entity type by creating a new record and checking numbering continuity.
Technical Changes
The analyzed specification defines an explicit maintenance action in setup for updating Pimics number series according to existing objects and configured numbering definitions.
Inheritance from Catalog Groups
Business Value
You can apply inheritance across catalog-group structures more broadly, reducing repeated maintenance of shared texts, features, and related content. This is valuable in hierarchies where shared information should be defined once and reused across child structures.
Includes controls and safeguards such as prevention of circular inheritance scenarios. For users, that improves maintainability without sacrificing data stability in deep category structures.
Where to start
- Select Search (Alt+Q), enter Catalog Groups (and related Chapter pages), and choose the related link.
- Open a parent catalog group and identify the inheritance-related setup fields or actions.
- Configure inheritance for one child structure and save the change.
- Verify inherited texts or features on the child record and confirm there is no circular setup.
Technical Changes
The specification describes inheritance enablement for Catalog Group -> Catalog Group and Catalog Group -> Chapter scenarios with control and validation updates.
Default inheritance and translate setup on existing items/nostock items after Pimics install
Business Value
You can initialize existing items and non-stock items after installation so inheritance and translation-related behavior aligns with intended default setup, not only with newly created records. This avoids inconsistent behavior between historical and new data.
This setup is moved into a controlled post-install and assisted setup flow, which helps teams complete initialization intentionally and reduces hidden configuration debt after deployment.
Where to start
PRECONDITIONS
Complete the assisted setup/post-install process before users start daily maintenance on existing items and non-stock items.
- Select Search (Alt+Q), enter Assisted Setup (or Pimics setup initialization page), and choose the related link.
- Open the Pimics initialization step for existing items and non-stock items.
- Run the setup action to apply default inheritance and translation behavior.
- Validate one existing item and one non-stock item to confirm expected defaults are active.
Technical Changes
Installation behavior changes in the PIMX Install codeunit that remove direct inheritance updates during install. The analyzed context ties this to a post-install setup flow and related setup-state logic.
Classification & Features
E-Class Import
Business Value
You can onboard E-Class classification data in a way that is closer to real customer datasets, reducing manual normalization work and improving practical usability of imported structures. This supports faster adoption of standardized classification models in product-data operations.
Where to start
PRECONDITIONS
Prepare the E-Class source file and confirm import mapping settings before you start the import.
- Select Search (Alt+Q), enter E-Class Import, and choose the related link.
- Open the import process and select your source dataset.
- Run an initial import.
- Verify class hierarchy and feature lookup behavior before full-scale import.
Technical Changes
Changed objects include the PIMX Class Card and PIMX Class List pages, PIMX Class Type enum, PIMX Class table, and feature/search-facing pages PIMX Feature List, PIMX Feature Group List, and PIMX Value List.
Includes hierarchy constraint adjustments and classification-ID lookup/search improvements. This indicates both structural model updates and usability-facing changes in feature/class browsing flows.
Mapping of Features
Business Value
You can map Pimics feature values from existing Item, Variant, and Catalog Item fields instead of entering values manually in every case. This supports more deterministic data population and reduces repetitive maintenance effort in large assortments.
Address source-priority and editability behavior, which is important for keeping mapped values stable when upstream records change. For users, this improves data consistency while preserving controlled override behavior.
Where to start
PRECONDITIONS
Mapping definitions between source fields and target features must be configured before users expect automatic value population.
- Select Search (Alt+Q), enter the feature-mapping setup page, and choose the related link.
- Open an existing mapping configuration for item, variant, or catalog-item source fields.
- Identify the source-priority and editability options and set them for one pilot feature.
- Recalculate or refresh one product and verify the mapped feature values.
Technical Changes
The analyzed specification describes mapped-value behavior, lookup of referenced fields, and synchronization direction between master data fields and product features.
Issues with Synchronize Features to Attributes and consistency
Business Value
You can keep feature-driven item attributes and their translations synchronized more reliably, reducing mismatches between Pimics feature data and BC attribute representations. This is particularly valuable in multilingual scenarios where translated labels and values must stay aligned.
Includes trigger points for sync-setting changes and translation update propagation, which reduces manual repair work and improves consistency across data-maintenance workflows.
Where to start
PRECONDITIONS
Synchronization settings between features and attributes must be enabled in setup before translation propagation can be expected.
- Select Search (Alt+Q), enter Catalog Setup (or feature synchronization setup), and choose the related link.
- Open synchronization settings and confirm how features should sync to attributes.
- Update one feature or translation value in a test scenario.
- Verify that related attribute and attribute-value translations are updated consistently.
Technical Changes
Changed objects include the PIMX Translation Management codeunit, PIMX Catalog Translation table, PIMX Item Attribute and PIMX Item Attribute Value table extensions, and PIMX Catalog Setup table.
These changes align with the described requirement to propagate feature and value translation updates into attribute and attribute-value translation records when synchronization is enabled, including behavior tied to setup defaults and feature-level sync modes.
Rules & Transformations
RegEx replacement support for rule action and import transformation
Business Value
You can perform richer text normalization by applying replacement-capable regular-expression transformations instead of extract-only pattern handling. This supports more practical data-cleanup scenarios in imports and rule-driven enrichment processes.
Users can keep current configurations while introducing advanced replacements where needed. This reduces custom workaround logic in external preprocessing steps.
Where to start
- Select Search (Alt+Q), enter the Rules page you use today, and choose the related link.
- Open an existing transformation rule where text cleanup is currently limited.
- Identify new RegEx replacement options and configure one replacement scenario.
- Test the transformation on sample input and verify output before rollout.
Technical Changes
The release includes new RegEx action parameters such as replacement behavior, match selection, and whole-input replacement mode, plus upgrade-safe default handling.
Integrations & API
Cross Reference entities with related data in API
Business Value
You can retrieve cross-reference entities with the context required for integration scenarios that need related data, reducing fragile post-processing in external services. This supports more complete API consumption in publication and channel integrations.
The approach also targets practical constraints around circular expansion in Business Central API design. For integrators, this improves predictability of how references and related records should be read in beta/2.1 flows.
Where to start
- Select Search (Alt+Q), enter the Pimics API setup or API documentation page, and choose the related link.
- Open the cross-reference endpoint you already consume.
- Identify newly available related-data fields and plan how your integration will read them.
- Test one request/response cycle in a non-production environment before deploying changes.
Technical Changes
The design specifies API behavior changes including removal of restrictive reference filters in items/categories endpoints, addition of reference-type context fields, and structural context in references responses.
Sana Commerce: Handle deleted data
Business Value
You can keep Sana channel data synchronized when records are deleted or detached, reducing stale products, relations, and content in storefront outputs. This is critical for predictable channel behavior in high-change environments.
Implementation covers deletion handling across items, cross-references, and related publication content, with emphasis on reliable change detection for update-index processing. For users, this reduces manual reindex interventions and support incidents caused by missed deletion propagation.
Where to start
PRECONDITIONS
Confirm your Sana synchronization job and publication update process are active before testing deletion propagation.
- Select Search (Alt+Q), enter Publications synchronization page, and choose the related link.
- Open an existing record that has related Sana channel data.
- Delete or detach the record in a controlled test case.
- Run synchronization and verify that storefront-related data is removed or updated correctly.
Technical Changes
The analyzed implementation notes reference publication-line change tracking as a key mechanism for detecting and propagating deletion impacts to affected items.
Option to enable/disable Sana web service log
Business Value
You can choose whether Sana request/response messages are logged, which helps balance diagnostics depth and operational overhead. This is especially important for customers with high request volumes where full XML logging can dominate activity logs and consume significant storage.
The process outcome is clearer operational control: keep detailed logs when troubleshooting, and reduce log noise during stable production periods while preserving error visibility.
Where to start
PRECONDITIONS
You need setup permissions to change Sana logging behavior.
- Select Search (Alt+Q), enter Catalog Setup, and choose the related link.
- Navigate to the logging option Log Web Service Messages´´** that controls request/response message storage.
- Enable logging for troubleshooting sessions or disable it for normal high-volume operation.
- Run one integration cycle and verify expected logging behavior in activity logs.
Technical Changes
The specification introduces a boolean setup field to control logging behavior in Sana publication context, and the linked discussion confirms that request/response logging should respect this field while error logging remains active.