invantive documentation
Invantive Support ForumsLog In / Sign Up

Release notes of Invantive Studio, 25.0 to 26.0

Release Note - Installer

Invantive Studio 26.0, from 25.0

Build Date Description
25.0.233 08-07-2026 last build of release 25.0
26.0.383 09-11-2026 last build of release 26.0

The 26.0 line also contains the builds 25.1.x of the preceding beta period (2025-09-01 to 2026-03).

  • 70 enhancements
  • 60 bug fixes
  • 6 things to check before upgrading

Before You Upgrade

These changes ask for a check:

Top 25 Changes

  1. Licence keys are validated by the Invantive License Service
    • Enhancement
    • Licences are validated and renewed through the central Invantive License Service instead of the CryptoLicensing method of release 25.0. The licence window and the status text show the licence number, contract code and origin, and the service decides which platform modules a licence includes. A key of the old format gets a message that explains how to continue. A valid licence stays in force for up to 24 hours when the service cannot be reached.
  2. Parts of a PSQL block can run in parallel
    • Enhancement
    • PSQL gets a PARALLEL construct that runs branches and loop iterations side by side. Failures of branches are collected and can be read afterwards. The new package dbms_atomic holds named values that parallel branches share safely.
  3. Left join without the word OUTER is no longer turned into an inner join
    • Bug Fix
    • A statement written as left join, right join or full join, without the word outer, was executed as an inner join. Rows without a match on the other side were lost without any warning.
  4. Saved credentials are stored in a new file that is the same on every system
    • Enhancement
    • action needed
    • Action needed before or after the upgrade.
  5. Data containers can be defined on Invantive Credentials Server
    • Enhancement
    • Connection details, licence checks and OAuth credentials are retrieved from Invantive Credentials Server instead of a local settings file. The connection list shows the server and database, log-on no longer asks for an alias for these data containers, a retrieval is repeated up to three times after a time-out, and the messages are clearer.
  6. Visma.net: new API generation, Visma Connect log-on, sales orders and time cards
    • Enhancement
    • The Visma.net driver uses the current API specification, signs on through Visma Connect and respects the limit of 15,000 calls per hour by waiting when it is used up. It adds tables for Sales Order V3 and for time cards, including filtering, paging, insert and update. A filter such as not equal on a column with a fixed list of values is turned into requests for the remaining values.
  7. A script can query its own execution profile
    • Enhancement
    • Runs of Invantive Script, their statements, started operating system commands and script variables are registered and can be queried with plain SQL through the new data container Script and the data dictionary. Duration, CPU use, rows touched, exit codes and output volume are available. Statement text can be anonymised and variable values masked.
  8. Exact Online incremental tables are no longer reloaded in full without need
    • Bug Fix
    • Incremental tables could be reloaded in full when the row count check gave a false alarm, when a rejected earlier version was not rewritten and when old deletions held the starting point back. These causes are repaired. The disk cache setting of the execution no longer switches off the incremental cache.
  9. Case expression uses the widest data type of all branches
    • Bug Fix
    • A case expression took the data type of the first branch with a type. A narrow first branch, such as a whole number, then cut the decimals of a wider branch evaluated later. The widest type of all branches is now used.
  10. Fix comparisons on the result of functions such as left, ltrim, rtrim and nvl
    • Bug Fix
    • A comparison on the result of left or a similar function could return no rows, and nvl on a nullable number could answer null instead of the replacement value. The trimming of constants now removes blanks only, as it does for columns.
  11. Resolve whole numbers in SQL as integers instead of decimals
    • Enhancement
    • action needed
    • Action needed before or after the upgrade.
  12. Take one size value in the QR code functions
    • Enhancement
    • action needed
    • Action needed before or after the upgrade.
  13. More database data types are recognised; an unsupported type raises an error
    • Enhancement
    • Reading from Oracle, SQL Server, PostgreSQL and other SQL databases recognises more data types, such as long, nclob, nvarchar2, sql_variant, interval types and anydata. An unsupported data type raises an error instead of being handled silently. Text columns have no precision and scale.
  14. Exact Online XML tables load faster
    • Enhancement
    • The XML tables of Exact Online can use a predefined list of fields instead of reading the schema first, controlled by the setting use-predefined-fields. Column positions are looked up once instead of per row.
  15. Lower memory use in long-running sessions
    • Enhancement
    • Identical text and binary values in the result of a long query are shared within one execution, the history of query plan statistics is limited in size and age, and a program that writes many different files no longer uses more and more memory.
  16. Oracle: tables and views with mixed-case names can be queried
    • Enhancement
    • Names of Oracle tables, views and owners that were created with a quoted mixed-case name are no longer forced to the standard casing. The name as typed and the name in the usual Oracle casing are both tried.
  17. Twinfield: more offices per session
    • Enhancement
    • The maximum number of Twinfield offices that one session can use with an application supplied by Invantive is raised from 37 to 370. The new setting additional-allowed-offices names further offices that may be used.
  18. Gripp CRM: more tables and fields and better server-side filtering
    • Enhancement
    • Gripp CRM gets additional tables, among them absence request lines and bulk prices. More filters are passed on to Gripp, which reduces the rows that are read.
  19. SnelStart: data model follows the API definition of 27 May 2026
    • Enhancement
    • The SnelStart tables and columns follow the newer API definition. More reference fields are available, decimal values are read as numbers and the purchase invoice number can have 60 characters.
  20. Better handling of OAuth token failures
    • Enhancement
    • A stalled token endpoint is cut off after 30 seconds and treated as a temporary error. A refresh token that is refused without an error code now asks for new authorisation, and unknown answers are logged in anonymised form.
  21. Exact Online incremental tables are written more safely
    • Enhancement
    • New chunks of an incremental table are written under a new generation, so the previous copy stays complete until the new one is listed and an interrupted load does not damage it. A new setting limits the age of deleted rows and raises message itgeneor878. The new table IncrementalEntityTypes lists the entity types that can be loaded incrementally.
  22. Safer handling of web requests
    • Enhancement
    • Web requests no longer accept Brotli compressed answers, because the Brotli decoder of .NET before 10.0.14 has a memory write flaw. Values of security-sensitive headers are masked in diagnostic output, and reading an answer ends with a time-out error when it does not finish in time.
  23. Apply the Twinfield office limit only to Invantive client identifiers
    • Bug Fix
    • The error about too many Twinfield offices was also raised when a customer used a client identifier of their own. The limit now applies only to Invantive's own client identifiers or when no identifier is known.
  24. Fix internal error and invalid file on Excel export
    • Bug Fix
    • An internal null reference error on exporting to Excel is avoided, and the exported file no longer carries an application version that Excel rejects.
  25. Licence modules for Matomo, Inspectlet, Nextcloud, Tweede Kamer v5, DeepL and LibreOffice
    • Enhancement
    • The licence system knows the platforms Matomo, Inspectlet, Nextcloud, a second Tweede Kamer driver for the v5.0 API, DeepL and the data tool LibreOffice. Licences can include or exclude them.

All Enhancements

Changes to behaviour, platforms, drivers and settings, grouped by area.

Importance: all | 2 and higher | 3 and higher | 4 and higher | 5

Platform: all | ActiveCampaign (1) | AFAS Online (1) | Brevo (1) | Chargebee (1) | Crisp (2) | Data Cache (1) | DeepL (1) | Exact Online (19) | File system (1) | Fortnox (1) | Gripp CRM (1) | HubSpot (1) | Inspectlet (1) | Invantive Script (1) | ionBIZ (1) | LDAP (1) | LibreOffice (1) | Loket (1) | Matomo (1) | Microsoft Access (1) | MySQL (2) | Nextcloud (1) | Nmbrs (1) | OData (1) | Odoo (1) | Oracle (6) | Outlook (1) | Pipedrive (1) | PostgreSQL (6) | SnelStart (3) | SQL Server (5) | Teamleader (1) | Teamleader Focus (1) | Tweede Kamer (1) | Twinfield (3) | VIES (1) | Visma Severa (1) | Visma.net (2) | Windows (1) | Yuki (3)

5 of 130 shown.

Platforms and drivers

More database data types are recognised; an unsupported type raises an error

Reading from Oracle, SQL Server, PostgreSQL and other SQL databases recognises more data types, such as long, nclob, nvarchar2, sql_variant, interval types and anydata. An unsupported data type raises an error instead of being handled silently. Text columns have no precision and scale.

  • MySQL
  • Oracle
  • PostgreSQL
  • SQL Server
  • importance 3
Upgrade the Oracle, SQL Server and Microsoft sign-in components

The Oracle data access component is upgraded from version 21 to version 23, the SQL Server management component from version 172 to 181 and the Microsoft sign-in library to a newer version. Behaviour of Oracle connections may differ slightly.

  • Oracle
  • SQL Server
  • importance 3
SQL Server driver uses the Microsoft client and reports a missing runtime clearly

The SQL Server driver now identifies itself with the current Microsoft client library instead of the older System library. When the client cannot be loaded on a computer, the driver raises a clear error instead of failing without a useful message.

  • SQL Server
  • importance 2

All Bug Fixes

Defects of the older release that are repaired.

SQL engine

Filter with like and not like on SQL Server and Access gives correct rows

A like or not like filter evaluated on the client treated upper and lower case the wrong way round, so rows such as A%B were dropped. For Microsoft Access, a not-equal filter is now sent in the standard form that Access can read.

  • SQL Server
  • Microsoft Access
  • importance 3

Platforms and drivers

Microsoft SQL Server: bulk insert and create table work with the updated driver

The SQL Server driver was updated to version 7.0.2 because version 7.0.0 had a problem with bulk insert and create table.

  • SQL Server
  • importance 3

What It Builds On

Kind Name From To
invantive component Invantive Studio 25.0.233 26.0.383
invantive component Invantive(R) Basics 25.0.233 26.0.383
invantive component Invantive(R) Producer GUI Base 25.0.233 26.0.383
invantive component Invantive(R) Producer Data Model 25.0.233 26.0.383
invantive component Invantive(R) Producer GUI 25.0.233 26.0.383
invantive component Invantive(R) SQL for Core 25.0.233 26.0.383
invantive component Invantive(R) SQL 25.0.233 26.0.383
invantive component Invantive(R) SQL for Windows 25.0.233 26.0.383
build tool Invantive Deploy 25.0.233 26.0.383
build tool change Windows installer now packages the .NET 10 build instead of the .NET Framework 4.8 build
build tool change Installer rejects more placeholder e-mail addresses and phone numbers
build tool change Log opened from the installer exit dialog ends with an 'End of File' line
build tool change Installer picks up language folders for Catalan, Hungarian and Romanian
build tool change List of supported Windows versions shown with the product is updated
third party summary

More Information

How This Note Was Made

  • For all products together 22 items whose changed lines are 50 to 70 % in the last build of 25.0 and 22 items that a content check would have left out were read against that build; the items that apply to this product are kept or left out on that reading.
  • Range: commits of origin/release-26.0 that are not in origin/release-25.0 and have no equivalent patch there (git cherry).
  • For a product that does not offer SQL to its users, items of the shared libraries outside the areas installation, licensing, security and diagnostics, and items about one platform, are left out and counted as internal.
  • The commits are the ones of the range that touch a project of the product; each commit was classified once, for all products, and the items of a product are the items that contain such commits.
  • Version stamp commits of the build pipeline are left out.
  • A change whose changed lines are for 70 % or more already in the first 26.0 build is left out; items between 50 % and 70 % and all such exclusions were checked by reading the code of that build.
  • A bug fix whose repaired lines were written by another commit of the same range is merged into its feature or left out.
  • Texts were written from the commit messages and from the changes themselves; items carry a confidence.
  • 476 links between a change and a source commit are recorded.