Release Notes 2026

The Business NXT MCP create_entity and update_entity tools can now create and update records in Data Model Extension (DME) tables. See MCP.

Added new argument subTableQuery for reports, to control how sub-tables are queried. See Reports.

Support for inserting empty records with {}, which creates records with only the primary key columns assigned a value.

Better support for flag fields with additional operations to set and clear individual bits. See Flag fields

Added support for the Finnish language in useModel.

Fix: For failed update operations, the items field (if requested) returns, for the failed row, the values of the row before the update operation.

Fix: The count aggregate can be used with columns of any type, not only numeric columns.

Pagination internally uses pagination for better performance. The change is transparent, only the content of the opaque cursors startPage and endPage is changed.

The Business NXT GraphQL API now enforces an AI permission setting per company. AI integrations — GAiA and the Business NXT MCP — only receive data when the corresponding Read or Write permission has been granted in the System information and Company tables. Requests without the permission are rejected at the API regardless of the signed-in user’s other Business NXT permissions. The setting can only be modified by a System supervisor and takes effect immediately.

crossReference is now creatable and stockBalance is now updatable via the Business NXT MCP. update_entity accepts DME extension columns (flat field names or the extensions array shape). create_entity and update_entity now default onError to FAIL_TABLE to prevent silent partial writes, and create_entity with dryRun returns the full server-computed shape including nested children and currency context. Relations from get_table_definitions now carry the queryName/relation hints needed to construct joinup/joindown queries.

Improved the error handling for mutations: onError argument to control the behavior when an error is encountered, and a clear indication of what records failed. See Inserts - Error Handling.

Added breakBy argument to reports, to control how report rows are grouped into sections (page breaks). See Reports.

The type of the _count filter in having arguments is defined as Int instead of the type of the field being counted. See Grouping - the having argument.

When the values / value argument is empty, no update is performed, affectedRows is 0, and a warning is returned (as part of extensions).

Added three documentation tools to the Business NXT MCP: get_table_documentation for plain-English field and workflow prose from doc.visma.net, search_documentation for free-text search over the same source, and get_field_values for enum/bitmask catalogues (with batch decoding via a fields array). New skills cover the supplier invoice approval flow and periodised accounting analysis (income statement, balance sheet, budget vs actual). execute_graphql_query gains a client-side @decodeBase64 directive for base64-wrapped blob fields. init_company now inlines the company’s behaviour-switch bitmasks, and get_skill surfaces an access warning when the signed-in user is missing permissions for the tables a skill needs.

Added Business NXT MCP limited availability.

Suport for ordering using aggregate functions. See Grouping - the orderBy argument.

Added sqlName for columns in useModel. See Model info - columns.

Added new arguments for executing reports: landscape, mergeDocuments, zipDocuments. See Reports.

Added support to specify suggested fields at record level with _suggest special field. See Suggested values.

Fix: lookup of relations in data model extensions.

Added support for query the data model extensions with useModel. See Selecting the model.

Added support for transactional operations over a session, using the edit cache, that can be saved or discarded when the session completes. See Edit cache.

Added support for generically querying data model extensions (DMEs) in the schema. Currently, DMEs are only available for selected customers. The schema extensions can be used (although not recommended) to query the core data model too. See GraphQL Extensions.

Using the value argument but without the filter argument in an update mutation now returns a warning (as part of extensions) because it may lead to unintentional updates of multiple records. This will become an error in the future.