Release notes of Teamleader Orbit
Driver Release Note
Teamleader Orbit 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 |
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.
- 3 changes
- 0 can break a statement
- 3 groups not available
This Note
Groups
- Data model
- Provider attributes
- Capabilities
- Performance 0
- Bug fixes 1
- Enhancements 2
- 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
- –
- not available
- Do my statements and views still work?
- Provider attributes
- –
- not available
- Do I have to change my connection string, provider file or settings?
- Capabilities
- –
- not available
- What can the driver do with a table?
- Performance
- 0
- Is it faster, and does it call the platform less?
- Bug fixes
- 1
- Is the defect that I met repaired?
- Enhancements
- 2
- 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
The data models of this step could not be compared, so changes of tables and columns that break a statement are not known. The data model of this driver comes from build 22.1.262-BETA+4120 in the 26.0 workspace and from build 22.1.262-BETA+4120 in the 27.0 workspace; the groups from model files need a model that a build of each release generated, and generating it needs an account that is not at hand.
No other change of this step is marked as breaking.
Top 3 Changes
Changes that can break a statement first, then by importance. Columns are summarised per table in the data model.
- Read Teamleader Orbit moments without a time zone as local time
- Bug fixes
- Importance 3 of 5.
- Report translated messages when user or mailbox information cannot be retrieved
- Enhancements
- Importance 2 of 5.
- Show the date the Teamleader Orbit driver was created and last reviewed
- Enhancements
- Importance 1 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.
Not available. The data model of this driver comes from build 22.1.262-BETA+4120 in the 26.0 workspace and from build 22.1.262-BETA+4120 in the 27.0 workspace; the groups from model files need a model that a build of each release generated, and generating it needs an account that is not at hand.
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.
Not available. The data model of this driver comes from build 22.1.262-BETA+4120 in the 26.0 workspace and from build 22.1.262-BETA+4120 in the 27.0 workspace; the groups from model files need a model that a build of each release generated, and generating it needs an account that is not at hand.
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.
Not available. The data model of this driver comes from build 22.1.262-BETA+4120 in the 26.0 workspace and from build 22.1.262-BETA+4120 in the 27.0 workspace; the groups from model files need a model that a build of each release generated, and generating it needs an account that is not at hand.
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.
- 0 changes
- commits
No changes in this group.
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.
- 1 changes
- commits
Read Teamleader Orbit moments without a time zone as local time
Teamleader Orbit sends moments without a time zone and means local time. The driver now says so, instead of assuming universal time, so such moments are no longer shifted.
- importance 3
- confidence low
Enhancements
What can I do now that I could not? New functions and options that are not a table or a column.
- 2 changes
- commits
Report translated messages when user or mailbox information cannot be retrieved
The error messages for failing to retrieve user information, mailbox information and invalid mailbox information are now available in the language of the user.
- importance 2
- confidence medium
Show the date the Teamleader Orbit driver was created and last reviewed
The registration of the driver holds the date it was created and the date it was last fully reviewed against the platform, both 6 September 2023.
- importance 1
- 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.
More Information
- Data model documentation of the driver
- Questions and answers on the forum
- Invantive Cloud page of the driver
- All release notes
How This Note Was Made
- TeamleaderOrbitRegularProvider.cs and TeamleaderOrbitReportingProvider.cs: DateTimeKindWhenPlatformStatesNone returns Local. The property is new in the shared base class in this range, so what 26.0 did for these moments was not established; the same commit also migrates the JSON reading (ODataV4WithOAuthProviderBase, JsonValueRef). Result values can change for existing statements.
- 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.
- 5 links between a change and a source commit are recorded.