Release Notes

2025.10.17

• Better error information by providing the name of fields whose assignment failed in create or update mutations. See Understanding error information.
• New fields identifier, domainTypeNo, and domainTypeNoAsEnum for domains in model information. See Model information.
• Fix: execution of queries when the sort sequence column is included in list of sort columns (orderBy argument).

2025.09.30

• Fix: passing input objects using variables for create or update mutations preserves the order of fields.

2025.09.23

• Introduced the orderBy argument for sorting the results of availableCompanies and availableCustomers queries to be consistent with arguments for connection types. The existing sortOrder argument is deprecated and will be removed in the future.
• Fix: the filtering of results on an update operation with an empty value \ values argument.

2025.09.17

• Support for creating head and line records (for order-order lines and batch-voucher) in a single insert operation. See Inserting head and line rows.
• Support for creating temporary records. See Temporary rows.

2025.09.11

• Improved support for async queries: multiple delete and insert/update operations can be executed in a single async request. See Async queries.

2025.09.05

• Support for comparing timestamp fields (createdTimestamp and changedTimestamp) with current date/time and better error messages for invalid ReferenceDateTime values. See Comparing with current date/time.

2025.09.02

• Return a warning (as part of extensions) for every deprecated feature used in a request. See Deprecated features.
• Fix: async requests with multiple insert/update operations return correct results.

2025.08.18

• GraphQL requests are dispatched to middleware service for processing, which can execute directly most reads (and other operations in the future) without sending them further to the VBus backend. This is the same execution improvement that was introduced for the front-end earlier this year.
• Upgraded GraphiQL web IDE to version 4.x.

2025.05.15

• Better error messages for some specific errors
• Fix: joined results when foreign key is not set (default value)

2025.01.30

• Change of access rights handling: tables that are not readable will no longer appear in mutations for create/update/delete. Processings and reports will also be unavailable for these tables. Columns that are not readable will not be available in input types for create and update operations.
• Support for enumeration type domains for columns, arguments, or result values. See enum fields.

2025.01.23

• Support for specifying that a field’s execution depends on another one. See the @dependsOn directive.
• Support for deleting an asynchronous request job. See deleting an asynchronous request.

2024.10.09

• Availability of new createdTimestamp and changedTimestamp datetime fields on all tables. See Date and time fields.
• Improved error messages for two scenarious where available companies cannot be fetched.
• Fix: date fields suffixed with AsDate return null if the date is invalid, instead of throwing an error. The situation can arrive when an invalid date was set in the system (a feature used in some limited scenarios). The actual date can still be fetched using the column field of type Int.

2024.07.19

• Support for specifying the language in useModel nodes with a numerical value (eg. 47 for Norwegian). See Language selection.
• Improved messages for some category of errors (context failures).

2024.06.27

• Support for inserting records in between existing ones. See Insert between existing records.

2024.06.20

• Extended model information with relations and domain members and access restrictions, availability, and additional properties for each entity type. See Model information.

• Fields assigned from unset variables are ignored in insert/update mutations. See Assigning fields from unset variables.

• Support for comparing date and time fields with the current date and time. See Comparing with current date/time.

• New argument orderBy for defining the sorting order of the results. See Sorting.

  Warning

  The previous sortOrder argument is deprecated and will be removed in the future.

• Fixed bug that affected blob fields: base-64 encoded values were stored instead of the actual binary data.

2024.05.30

• Support for fetch distinct values using a new query argument called distinct. See Distinct values.

  Warning

  The previous schema section for aggregates, which includes distinct, is obsolete and will be removed in the future. See Aggregates.

• Fix: incorrect results when filtering with _is_null / _is_not_null on blob columns.

2024.05.23

• Support for _in / _not_in operators in having expressions.
• Support for _between / _not_between operators in filters and having expressions. See Filtering: _between / _not_between operators.
• Support for domain information in the model. See Model information.
• Eased some limitations on async requests. See Async queries.
• Defined a limit of 32 requests in a batch. See Batched requests.
• Improved description of table columns in the schema. See Understanding column descriptions

2024.03.07

• Async queries return correct results when fetching data from multiple tables in a single query. Also the totalCount fields works as expected. See Async queries.
• Added createdDateTimeUtc and changedDateTimeUtc as well as createdDateTimeTZ and changedDateTimeTZ for filters. See Datetime special fields.
• Performance improvement for pagination when hasNextPage is requested. For tables of tens of millions of records, the execution time is reduced with 20-25 seconds.
• Empty arrays for _in and _not_int comparison operators in filter result in no data being returned. See Filtering.
• Fixed Illegal query bug for some queries that fetch aggregates using the group by feature.
• Fixed Unknown company error when a join operation (joinup_ or joinddown_ field) is used in the projection a mutation request.

2024.01.25

• Added support for grouping by data. See Grouping.
• Define changedDateTime with second and millisecond precision for table that include the changeTimeInMs column. See Date and time fields.
• Removed the restriction of executing a single async query at a time. See Async queries.
• The path of a failed assignment in an update request (index of record) included an error object. See Error handling.
• The path of a failed assignment in a create or update request included the error object when the operation is executed asynchronously.

2023.12.07

• Support for collecting multiple edits in a single update operation. See Update operations.
• Increased internal execution timeout to 59 seconds to allow longer synchronous operations. This value may be subject to change. Async queries are recommended for long running operations.

2023.10.26

• Fix: Support for bitflag values passed in query variables. See Bitflags.

2023.10.19

• Support for exporting values to an array variable. See the @export directive.

2023.10.05

• Fix: correct handling of filters with changedDateTime/createdDateTime and other _or expressions

2023.09.28

• Include name of status codes (with status_name) in error data not just status codes. See Error handling.

2023.09.07

• Fix: support for byte values in processing/report arguments
• Fix: partially finish order

2023.08.24

• Fix: hasNextPage report correct value when all data has been fetched
• Fix: allow more field to be set to null in order to request to suggest value

2023.07.20

• Support for batching multiple requests together. See Batched requests.

2023.07.06

• Support for skipping records. See Pagination.
• Better support for working with bit flags columns. See Bitflags.

2023.06.29

• Support for fetching model information. See Model information.

2023.06.01

• Support for _in and _not_in operators in filters. See Filtering.

2023.04.27

• Added a new way to suggest values in the correct field order using null values. See Suggested values.

• Deprecated the suggest argument for suggesting values.

  Warning

  the suggest argument will be removed in the future.

• Removed the deprecated suggestValues argument for suggesting values.

2023.02.09

• Added support for fetching distinct values. See Distinct values.

2023.01.05

• The availableCustomers field works for service-to-service integrations.
• The availableCompany returns all the companies from all customers if no customer ID was provided, not just the companies of the first found customer (as previously available).
• Company information from the availableCompanies field includes customer ID with the vismaNetCustomerId field.

2022.12.15

• breaking change: Access to system tables available under the new useCustomer field both for queries and mutations. See Accessing system tables

2022.11.10

• Better support for suggesting values with the suggest argument. The previous suggestValues argument is deprecated and will be removed after 1 March 2023. See Suggested values.
• Fix for @export directive. Nodes using exported variables execute only after variables have been resolved.

2022.09.29

• Improved performance for queries containing joins. See Unoptimized queries.
• Added the creation and completion time in the result value for asynchronous queries. See Async queries.
• Fix for mutations timeout when a record is not found.

2022.08.25

• Support for fetching available companies when using client credentials grant type for the access token (for service-to-service integrations). See Fetching user’s available companies.
• Added the @export custom directive. See Directives.

2022.08.04

• Support for suggesting values when inserting new rows. See Suggested values.
• Full support for aliases in queries. See Aliases.

2022.07.08

• Support for asynchronous queries. See Async queries.
• Added Brotli compression for all responses.

2022.05.26

• Support for service-to-service integrations. See Service integrations.