Release notes of Fortnox
Driver Release Note - Cloud
Fortnox driver 27.0, from 26.0
| Build | Date | Description |
|---|---|---|
26.0.4 |
22-03-2026 | first build of release 26.0 |
27. |
10-11-2026 | latest build of release 27.0 at the time of writing |
Data models compared: 26.0.340-PROD+6295 and 27.0.6-PROD+6293.
The older end is the first build of release 26.0, not its last, because later builds of 26.0 received ports of changes made for 27.0. The data model of a release is the model that a later build of the same release generated.
- 11 changes
- 3 can break a statement
- 0 groups not available
This Note
Groups
- Data model 5
- Provider attributes 2
- Capabilities 0
- Performance 2
- Bug fixes 0
- Enhancements 1
- Log-on and platform 1
More
What Changed, by Group
Every change is in one group: the group answers the question that you ask before you upgrade.
- Data model
- 5
- 3 can break a statement
- Do my statements and views still work?
- Provider attributes
- 2
- Do I have to change my connection string, provider file or settings?
- Capabilities
- 0
- What can the driver do with a table?
- Performance
- 2
- Is it faster, and does it call the platform less?
- Bug fixes
- 0
- Is the defect that I met repaired?
- Enhancements
- 1
- What can I do now that I could not?
- Log-on and platform
- 1
- Do I have to log on again, or change something because of the platform?
Download Changes as CSV | Data Model of Fortnox
Before You Upgrade
These changes can stop an existing statement, view, connection string or script from working:
- Column DUMMY is removed from Fortnox.CustomerReferences.CustomerReferenceById
- Check statements, views and scripts that use it before the upgrade.
- Column DUMMY is removed from Fortnox.CustomerReferences.CustomerReferences
- Check statements, views and scripts that use it before the upgrade.
- Column DUMMY is removed from Fortnox.TrustedEmailSenders.Senders
- Check statements, views and scripts that use it before the upgrade.
Top 8 Changes
Changes that can break a statement first, then by importance. Columns are summarised per table in the data model.
- Column DUMMY is removed from Fortnox.CustomerReferences.CustomerReferenceById
- Data model
- Breaks an existing statement or script.
- Column DUMMY is removed from Fortnox.CustomerReferences.CustomerReferences
- Data model
- Breaks an existing statement or script.
- Column DUMMY is removed from Fortnox.TrustedEmailSenders.Senders
- Data model
- Breaks an existing statement or script.
- Warehouse scopes and Recurring Billing, Integration Developer user endpoints added
- Log-on and platform
- Importance 4 of 5.
- Attribute max-discovered-column-count is added
- Provider attributes
- Importance 3 of 5.
- Lower memory use when reading JSON answers
- Performance
- Importance 2 of 5.
- Request limit window of 5 seconds declared
- Performance
- Importance 2 of 5.
- Throughput figures of Fortnox tables included
- Enhancements
- Importance 2 of 5.
Data model
Do my statements and views still work? Tables, views, table functions, columns, parameters, keys, code values, packages and procedures that appear, disappear, are renamed or change type.
- 5 changes
- model files
Columns
0 added, 3 removed, 2 changed, in 4 tables.
Fortnox.CustomerReferences.CustomerReferenceById: 0 added, 1 removed, 0 changed
Fortnox.CustomerReferences.CustomerReferenceById: 0 added, 1 removed, 0 changed-DUMMY
Fortnox.CustomerReferences.CustomerReferences: 0 added, 1 removed, 0 changed
Fortnox.CustomerReferences.CustomerReferences: 0 added, 1 removed, 0 changed-DUMMY
Fortnox.Native.NATIVEPLATFORMSCALARREQUESTS: 0 added, 0 removed, 2 changed
Fortnox.Native.NATIVEPLATFORMSCALARREQUESTS: 0 added, 0 removed, 2 changed~DURATION_MS(database_data_type:int64→double)~DURATION_MS(dotnet_data_type:int64→double)
Fortnox.TrustedEmailSenders.Senders: 0 added, 1 removed, 0 changed
Fortnox.TrustedEmailSenders.Senders: 0 added, 1 removed, 0 changed-DUMMY
Provider attributes
Do I have to change my connection string, provider file or settings? Attributes of the connection and settings of the driver that appear, disappear or change default or place where they can be set.
- 2 changes
- model files
Engine-wide connection attributes change
28 attributes added, 3 removed and 5 settings of attributes changed. These attributes belong to the SQL engine and exist for every driver; the Query Tool notes describe them.
- importance 2
Attribute max-discovered-column-count is added
Can be set from connection string, SET statement, provider file, log-on. Default 250.
- importance 3
Capabilities
What can the driver do with a table? Whether a table or table function can be selected from, inserted into, updated and deleted from.
- 0 changes
- model files
No changes in this group.
Performance
Is it faster, and does it call the platform less? Paging, batching, caching, filters and projections sent to the platform, fewer requests, less memory.
- 2 changes
- commits
Lower memory use when reading JSON answers
The driver reads the answers of Fortnox with a lighter JSON reader that allocates less memory. The error messages of Fortnox and the log-on information are also read with the shared default JSON settings.
- importance 2
- confidence medium
Request limit window of 5 seconds declared
The driver now declares that Fortnox allows 25 calls per 5 seconds, instead of using the shared default window of 60 seconds for the specification of the limit.
- importance 2
- confidence medium
Bug fixes
Is the defect that I met repaired? Wrong or missing rows, wrong values, crashes and wrong messages, repaired in a release line that had the defect.
- 0 changes
- commits
No changes in this group.
Enhancements
What can I do now that I could not? New functions and options that are not a table or a column.
- 1 changes
- commits
Throughput figures of Fortnox tables included
The driver carries measured figures for latency and rows per minute of its main tables, taken from logged sessions of June to October 2026. The engine uses such figures to estimate how long a statement takes.
- importance 2
- confidence medium
Log-on and platform
Do I have to log on again, or change something because of the platform? Log-on and token handling, scopes and permissions, a new version of the platform API, retired endpoints and changed limits.
- 1 changes
- commits
Warehouse scopes and Recurring Billing, Integration Developer user endpoints added
Fortnox starts enforcing the scopes for Warehouse and time reporting calls on 30 September 2026. The driver now asks for the Warehouse scopes as well, knows which licences they belong to, and maps the new Recurring Billing and Integration Developer endpoints. It also lowers the page size to the maximum that an endpoint declares, because Fortnox refuses the whole request when a page is larger.
What to Do
Authorise the Fortnox connection again when Warehouse data is needed, so that the new scopes are granted. Without the scope, queries on Warehouse tables return no rows instead of an error.
- importance 4
- confidence medium
In Numbers
Objects of the data model at both ends of the step.
| Objects | 26.0 | 27.0 | Change |
|---|---|---|---|
| tables | 1 | 1 | +0 |
| views | 11 | 11 | +0 |
| table functions | 0 | 0 | +0 |
| columns | 6,187 | 6,184 | -3 |
| function parameters | 1,581 | 1,581 | +0 |
| attributes of driver | 0 | 1 | +1 |
| tables that can insert | 52 | 52 | +0 |
| tables that can update | 39 | 39 | +0 |
| tables that can delete | 28 | 28 | +0 |
More Information
- Data model documentation of the driver
- Questions and answers on the forum
- Invantive Cloud page of the driver
- Documentation of the platform
- All release notes
How This Note Was Made
- 2026-11-01T10:15:08.9547122Z
- 2026-11-01T10:10:46.9788118Z
- Fields that only the newer model has.
- Fields that only the newer model has.
- Fields that only the newer model has.
- Fields that only the newer model has.
- Fields that only the newer model has.
- Fields that only the newer model has.
- Fields that only the newer model has.
- Commit items were classified by one reader; the model changes are derived and need no reading.
- Commits: the commits of the driver directory in the range that have no equivalent patch in the older state, without merges and version stamps; each was classified by reading its message and change.
- Model: the NDJSON files of data-models/database of the workspace of each release are compared record by record; only fields that both models have are compared, and texts are counted, not listed.
- A model generated from a later build of the same release (for example 26.0.340 for 26.0) stands for the release.
- 9 links between a change and a source commit are recorded.