Update 29.0.202645.181851

Prev Next

Release Date: 4. November 2026

Release Summary


Project specification fields now appear directly on the Project Card and List, and item numbers with parentheses import correctly again.

This release also fixes attachment retrieval through SharePoint and Azure Storage, posted sales document fields, and image previews in the Images factbox.

New Feature


Specification fields on Projects

You can now map Specification values to native fields that appear directly on the Project Card and Project List, matching the existing support for Customers, Vendors and Items, instead of only on the separate Specifications page. Map a value to one of the 24 available fields in the Specifications-on-Pages setup to show it there.

Specification fields kept in sync when validated by another app

Specification field values on documents such as the Sales Order now stay in sync, including any correction Master Data Information applies to the entered value, when another Abakion app validates them through Master Data Information's cross-app integration. Other apps can also show which Specification fields are set up for a table. Requires a connected app that uses this integration.

Bug Fixes


Import items with parentheses or other special characters in the item number

You can now import Master Data Information for items whose number contains parentheses or other special characters, such as V-112-M(2), without the import failing with a filter error, including through the Update Merge Descriptions action on the Master Data Information - Information Entries and Information Setup Card pages. Applies to the Master Data Information - Import Worksheet as well.

Retrieving attached files through SharePoint or Azure Blob Storage

Fixed an issue where retrieving a file already attached to a record failed with an "item with the same key has already been added" error. Applies to the File Placement field on Master Data Information entries, values and codes, when Default File Open Action on the Master Data Information Setup page is set to select or upload directly via SharePoint or Azure Blob Storage.

Correct attachment imports when using Azure Storage File Account

Fixed an issue where attachments for File-type Information Values stored via an Azure Storage File Account were missing or failed to open after being imported onto an Information Entry. Applies when using the Carry out actions action on the Master Data Information - Import Worksheet page, with the Azure Storage File Account feature enabled.

Why it matters: Entries imported before this fix keep their incorrect stored path and are not corrected automatically; re-import them through the Import Worksheet to fix the attachment.

Correct Subtype saved for programmatically created Information Codes

Fixed an issue where an Information Code created in code (for example by demo-data setup) always ended up with Subtype set to Specification, even when Text or File had been explicitly set; this also affects the Subtype an Information Entry inherits when it refers to such a code. Applies to the Master Data Information - Information Codes page and codes created programmatically.

Reliable image preview for externally linked pictures

Fixed an issue where a valid picture linked by URL could fail to appear because a slow response from the image server caused it to be hidden. Appears wherever the Images factbox is shown, for example on the Item Card.

Specifications on Pages fields filled automatically on posted sales documents

Fixed an issue where a Specifications on Pages field set up only on a posted sales document table, and not on the Sales Header, stayed empty after posting until you ran Update Field Value manually on the Specifications-on-Pages setup page. Posting a sales invoice, credit memo or shipment now fills that field automatically from the customer's information.

Why it matters: This applies only to posted sales document headers (invoice, credit memo and shipment) — posted sales lines and purchase documents are not covered yet.

Clear error when a master data value is too long for its field

Fixed an issue where entering, importing, or copying a master data value longer than its field allowed could raise an unexpected error or silently cut the value short; this could happen on the Master Data Information - Import Worksheet, in the Create New Specification guide, and on the Order Matrix. These now show an error naming the field and its maximum length, or shorten the value automatically where doing so is harmless.

Why it matters: Creating a new Item Attribute from an Information Code with a name too long for the Item Attribute table is now rejected with an error instead of being silently cut short, so check any such names you relied on being truncated automatically.