Release notes of SnelStart
Driver Release Note - Cloud
SnelStart 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.
- 17 changes
- 6 can break a statement
- 0 groups not available
This Note
Groups
- Data model 5
- Provider attributes 2
- Capabilities 0
- Performance 2
- Bug fixes 3
- Enhancements 5
- Log-on and platform 0
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
- 3
- 1 can break a statement
- Is the defect that I met repaired?
- Enhancements
- 5
- 2 can break a statement
- What can I do now that I could not?
- Log-on and platform
- 0
- Do I have to log on again, or change something because of the platform?
Before You Upgrade
These changes can stop an existing statement, view, connection string or script from working:
- Column DUMMY is removed from SnelStart.Echo.EchoInput
- Check statements, views and scripts that use it before the upgrade.
- Column DUMMY is removed from SnelStart.Relaties.RelatieCustomFieldsByRelatieId
- Check statements, views and scripts that use it before the upgrade.
- Column DUMMY is removed from SnelStart.Verkoopfacturen.VerkoopFacturenAlsUblById
- Check statements, views and scripts that use it before the upgrade.
- Date and time values of SnelStart are read as local time
- Check statements that compare date-time columns of SnelStart with moments in universal time; the values can differ by the offset of the time zone.
- SnelStart: more filters sent to the platform, and tables without fields left out
- Use the tables RelatieKlantCustomFieldsByRelatieId and RelatieLeverancierCustomFieldsByRelatieId instead of RelatieCustomFieldsByRelatieId; the connection test table EchoInput is no longer usable.
- A very slow view of SnelStart is no longer offered
- Do not use the view KolommenBalansPerPeriodeKostenAnalyse; use the other balance views.
Top 14 Changes
Changes that can break a statement first, then by importance. Columns are summarised per table in the data model.
- Date and time values of SnelStart are read as local time
- Bug fixes
- Breaks an existing statement or script.
- Column DUMMY is removed from SnelStart.Echo.EchoInput
- Data model
- Breaks an existing statement or script.
- Column DUMMY is removed from SnelStart.Relaties.RelatieCustomFieldsByRelatieId
- Data model
- Breaks an existing statement or script.
- Column DUMMY is removed from SnelStart.Verkoopfacturen.VerkoopFacturenAlsUblById
- Data model
- Breaks an existing statement or script.
- SnelStart: more filters sent to the platform, and tables without fields left out
- Enhancements
- Breaks an existing statement or script.
- A very slow view of SnelStart is no longer offered
- Enhancements
- Breaks an existing statement or script.
- Empty identifiers answered by SnelStart no longer stop a statement
- Bug fixes
- Importance 4 of 5.
- Count of rows on SnelStart reads only the identifiers
- Performance
- Importance 3 of 5.
- New view with the article lines of sales invoices made from sales orders
- Enhancements
- Importance 3 of 5.
- SnelStart data model follows the API specification of 27 May 2026
- Enhancements
- Importance 3 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.
- Invoice numbers of up to 60 characters fit in the SnelStart data model
- Bug fixes
- Importance 2 of 5.
- Throughput figures of SnelStart 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.
SnelStart.Echo.EchoInput: 0 added, 1 removed, 0 changed
SnelStart.Echo.EchoInput: 0 added, 1 removed, 0 changed-DUMMY
SnelStart.Native.NATIVEPLATFORMSCALARREQUESTS: 0 added, 0 removed, 2 changed
SnelStart.Native.NATIVEPLATFORMSCALARREQUESTS: 0 added, 0 removed, 2 changed~DURATION_MS(database_data_type:int64→double)~DURATION_MS(dotnet_data_type:int64→double)
SnelStart.Relaties.RelatieCustomFieldsByRelatieId: 0 added, 1 removed, 0 changed
SnelStart.Relaties.RelatieCustomFieldsByRelatieId: 0 added, 1 removed, 0 changed-DUMMY
SnelStart.Verkoopfacturen.VerkoopFacturenAlsUblById: 0 added, 1 removed, 0 changed
SnelStart.Verkoopfacturen.VerkoopFacturenAlsUblById: 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
Count of rows on SnelStart reads only the identifiers
A statement that counts the rows of a table asks SnelStart for the identifiers only. In the example of the code this is 93 bytes instead of 1 119 for two articles.
- importance 3
- confidence high
Lower memory use when reading JSON answers
The driver reads SnelStart answers with the lighter JSON reader of the engine.
- 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.
- 3 changes
- commits
Date and time values of SnelStart are read as local time
SnelStart answers a moment without stating an offset and means local time by it. The driver assumed universal time, so the moments could be off by the time zone difference. They are now read as local time.
What to Do
Check statements that compare date-time columns of SnelStart with moments in universal time; the values can differ by the offset of the time zone.
- can break a statement
- importance 4
- confidence medium
Empty identifiers answered by SnelStart no longer stop a statement
SnelStart answers an empty identifier, such as a country, as an all-zero value. Reading customers, relations, sales orders or quotations failed because of it. The value is now read as empty.
- importance 4
- confidence high
Invoice numbers of up to 60 characters fit in the SnelStart data model
The data model allowed purchase invoice numbers of 25 characters. It now allows 60, as SnelStart does.
- importance 2
- confidence medium
Enhancements
What can I do now that I could not? New functions and options that are not a table or a column.
- 5 changes
- commits
New view with the article lines of sales invoices made from sales orders
The new view gives the article lines of every sales invoice that was made from a sales order, 500 orders per request. SnelStart answers no lines on a sales invoice itself. An invoice entered without an order has no row.
- importance 3
- confidence high
SnelStart data model follows the API specification of 27 May 2026
The tables and columns are built from the updated SnelStart API specification. Reference columns are read up to five levels deep, while links (uri) are skipped because the identifier is there already.
- importance 3
- confidence medium
SnelStart: more filters sent to the platform, and tables without fields left out
More filters are sent to SnelStart, among them on the lines of sales orders and on price agreements. The documents of bookings and relations no longer fail on an empty parent. Two tables that answer only text or lists without fields (a connection test and a list of custom fields that is available under two other names) are left out instead of failing every statement.
What to Do
Use the tables RelatieKlantCustomFieldsByRelatieId and RelatieLeverancierCustomFieldsByRelatieId instead of RelatieCustomFieldsByRelatieId; the connection test table EchoInput is no longer usable.
- can break a statement
- importance 3
- confidence low
A very slow view of SnelStart is no longer offered
A balance view per period for the cost analysis was very slow and tentative for users. It is switched off.
What to Do
Do not use the view KolommenBalansPerPeriodeKostenAnalyse; use the other balance views.
- can break a statement
- importance 2
- confidence low
Throughput figures of SnelStart tables included
The driver carries measured latency and rows-per-minute figures, so that the engine can 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.
- 0 changes
- commits
No changes in this group.
In Numbers
Objects of the data model at both ends of the step.
| Objects | 26.0 | 27.0 | Change |
|---|---|---|---|
| tables | 10 | 10 | +0 |
| views | 9 | 9 | +0 |
| table functions | 0 | 0 | +0 |
| columns | 2,429 | 2,426 | -3 |
| function parameters | 224 | 224 | +0 |
| attributes of driver | 2 | 3 | +1 |
| tables that can insert | 9 | 9 | +0 |
| tables that can update | 7 | 7 | +0 |
| tables that can delete | 7 | 7 | +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-01T12:04:38.5636546Z
- 2026-11-01T11:53:49.7141715Z
- 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.
- 229 lines in provider and throughput file: parentIdentifier empty Guid handling (itgenodr028), SetPrijsafspraakFilterName, GetTopLevelFieldName, ancestor source paths for the lines tables, and a switch that returns no object definition for EchoInput and RelatieCustomFieldsByRelatieId. The model diff lists the DUMMY column of exactly these two tables as removed, but the model of 27.0 was generated on 2026-11-01 and this commit is dated 2026-11-04, so this commit cannot be the cause. Whether the two tables are still listed was not checked.
- In the code the view definition is commented out with the text Disabled since it is very slow and tentative for users; the rest of the commit reformats the table name mapping (266 lines). Ported to release-26.0, so the model diff does not show the removal. The view name is from the commented-out code; whether another view replaces it was not checked. Also ported to origin/release-26.0 (after the first build of 26.0): dc2b118687 as 67b19fa7a1. The step is measured from the first build, so the item stays; the model diff compares 26.0.340 with 27.0.6 and does not show what the ported commits changed.
- 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.
- 16 links between a change and a source commit are recorded.