We like to priovide you with the version history of our 5.8.0 release. Simply click the link below to access the corresponding .pdf file:
iPIM Portal
[Report] New option to export individual rows of report results via the standard export dialog
Users can now export partial report results in iPIM Web by selecting specific rows before downloading. Previously, reports could only be downloaded in their entirety. The new functionality utilizes the standard table export dialog and applies the same handling logic for large datasets as the existing export feature. This update enables targeted data extraction after filtering or selecting specific report entries.
[iPIM Web] The multi edit bar in the “Product details” app now now the active context
The multi edit bar in the “Product details” app now now the active context that was selected in the “Selection” widget.
[iPIM Portal] In the “Product details” app, newly added suppliers are selected automatically.
After adding a new supplier using the 
button in the “Product details” app, the interface automatically selects the newly added supplier. This eliminates the previous requirement for master data editors to manually switch the active supplier before editing attributes. The update streamlines daily workflows by removing this unnecessary step, improving overall user experience without altering core functionalities.
iPIM Supply
Export of the transformation report now includes filtering of item notifications by error code
The iPIM Supply transformation report now includes a filter for error codes when exporting the error report. Users can select a single error code from a new dropdown menu. Only items and messages matching the selected code are exported, addressing issues where large reports previously exceeded Excel file limits. This feature applies exclusively to the item messages export and supports single-code selection only.
The import process now features a “skip unchanged items” option for assortment updates.
The import process now features a “skip unchanged items” option for assortment updates. By default, the system generates a data hash for each incoming item and compares it against the stored database entry. When no changes are detected, database writes and downstream synchronization are bypassed. This optimization significantly reduces processing overhead for large, stable catalogs. A dedicated configuration checkbox and associated user permission allow teams to control this behavior.
