Update 27.1.202550.150560

Users creating new Item Variants via “Suggest new records” in the Item Variant Creation Worksheet (accessible from the Item Card) can now build filter strings more efficiently by selecting multiple Information Values.

On the SCB Create Record Filters page (ID 6082945, StandardDialog), the fields labeled “Master Data Information” now support multi-selection in the lookup.

An upgrade unit has been implemented to automatically update all existing Information Entries with blank Key Fields, ensuring these fields are populated with the correct related record ID. This change brings historical data in line with current validation rules and improves overall data integrity for master data users.

We have aligned the sorting behavior between the following pages:

• SCB Edit Master Data Arc Entr (6223594, List)

• SCB Master Data Archive Entries (6083251, List)

This also applies when opening archived entries via Specifications → Archived Entries.

What’s changed

• The default sort order is now consistent across both lists.

• When navigating through Specifications → Archived Entries, the archive entries are presented in the same order as on the master archive list page.

• Users will experience predictable and uniform sorting of archived master data entries, making it easier to review and compare records across the two list pages.

We have fixed an error that could occur when deleting SCB Information Entry records that contained empty values.

What’s changed

• When an Information Entry is deleted, the cleanup logic (CleanUpMasterRecordFromInformationEntry) now handles empty values safely when clearing related fields on the master record.

• Previously, the system attempted to convert an empty string to typed values (such as Boolean, Decimal, Integer, Date, DateTime, DateFormula) during cleanup.

  • This could cause a runtime error, especially for Boolean fields, because converting an empty string to a Boolean is not allowed.

• The update logic has been adjusted so that empty values are processed without using invalid conversions, preventing these errors.

This ensures that deleting Information Entries will clean up related master data fields reliably, even when entries contain empty values.

We have fixed several issues related to how Master Data is transferred and shown on sales documents and related warehouse documents.

What’s changed

• Master Data specifications entered on a Sales Quote are now correctly:

  • Transferred to the Sales Order when converting the quote to an order

  • Shown in the Specifications on Pages fields (SCB MDI Field 1–24) on the Sales Order header

• Replication of Master Data between:

  • Customer → Sales Header

  • Item → Sales Line

  • Sales Header/Lines → Warehouse Shipment Header/Lines

    has been corrected so that all relevant fields are now consistently inherited when the setup in Master Data on Documents and Master Data on Document Template is in place.

• Fixed a validation error where fields were incorrectly treated as a different data type (e.g. DateFormula instead of Decimal), which could cause errors when inserting items.

• Corrected handling of Boolean fields so their values are now consistently aligned between source records (e.g. Customer) and the created Sales documents.

These improvements ensure that Master Data flows reliably across quotes, orders, and warehouse documents, and that what you see in the Specifications fields matches the underlying Master Data on Documents.

We have fixed an issue in Master Data Information where the system prompted for validation on every single line when using “Add Values to Lines” in the Information Matrix after upgrading from version 26.5.202541.144373 to 27.1.202547.148535.

What’s changed

• The “Add Values to Lines” function now updates lines without triggering a separate validation dialog for each line.

• The behavior is back in line with previous versions, so users can again update many lines in one operation without repetitive pop-ups.

• This improves efficiency and makes it easier to maintain larger sets of master data in the Information Matrix.

We have fixed an issue where the Description field was truncated when creating a new Item Variant from a Style Master.

What’s changed

• The Description on Item Variants created from a Style Master now supports the full 100 characters during creation.

• Previously, the Description was cut off at 50 characters, even though it could be manually extended to 100 characters after creation.

This ensures that long descriptions are preserved immediately when creating Item Variants, reducing the need for manual corrections.