invantive documentation
Invantive Support ForumsLog In / Sign Up

Release notes of Crisp

Driver Release Note - Cloud

Crisp driver 27.0, from 26.0

Build Date Description
26.0.4 22-03-2026 first build of release 26.0
27.0.93 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.

  • 6 changes
  • 0 can break a statement
  • 3 groups not available

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
    • 2
    • Is it faster, and does it call the platform less?
  • Bug fixes
    • 2
    • 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?

Download Changes as CSV | Data Model of Crisp

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 none in the 26.0 workspace and from build 26.1.88-BETA+6212 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 6 Changes

Changes that can break a statement first, then by importance. Columns are summarised per table in the data model.

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 none in the 26.0 workspace and from build 26.1.88-BETA+6212 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 none in the 26.0 workspace and from build 26.1.88-BETA+6212 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 none in the 26.0 workspace and from build 26.1.88-BETA+6212 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.

  • 2 changes
  • commits

Date conditions on conversations are sent to Crisp as a date range

A condition on the date of a conversation is now also sent to Crisp as the start and end of the date range of the conversation list, so that pages that cannot contain matching rows are not fetched. The condition is still checked on the retrieved rows. A new connection attribute, forward-filters-as-table-function-parameter, switches this on or off (on by default).

  • importance 3
  • confidence high
Crisp JSON is read with System.Text.Json and fewer memory allocations

The driver reads Crisp answers with a different JSON reader that allocates less memory. Test runs with both readers gave the same results.

  • 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.

  • 2 changes
  • commits

Crisp rate-limit refusals (HTTP 423) are waited out instead of ending the statement

When Crisp refused a request because too many were sent, the driver treated it as a spent daily quota and stopped the statement at once. Measurements show the refusal clears within tens of seconds, so the driver now waits between 30 seconds and 2 minutes and retries within the retry budget of the connection. Reading large tables no longer fails after a burst of requests.

  • importance 4
  • confidence high
Clearer Crisp errors for invalid email, too high page number and missing website ID

Errors for an email address with a wrong format and for a page number beyond the last page now have their own message. The message for a missing website ID names Crisp and the website ID is checked for the GUID format when it is set.

  • 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.

  • 2 changes
  • commits

More than 50 new Crisp tables and table functions, with larger pages

The Crisp driver now covers many more routes of the Crisp API, among them conversations and their messages, files, events and relations, people profiles with their data, events and subscriptions, operators and inboxes, visitors, the helpdesk, campaign templates and website settings. Lists are read in pages of 50 rows instead of 100 rows; messages of a conversation are paged by timestamp.

  • importance 4
  • confidence high
Functions to clear the phone, gender, notepad and company domain of a Crisp person

Four new functions clear one field of a people profile by sending an empty value, which is the only way Crisp accepts for removing it. The employee count cannot be cleared through the Crisp API.

  • importance 2
  • confidence high

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

How This Note Was Made

  • 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.
  • 10 links between a change and a source commit are recorded.