L2025.2 Release Notes

Pre-Release

These release notes are being provided in advance of the release, for your preparation and evaluation of the upcoming version. This version will be released for Cloud Availability shortly.

As the content is still in progress, it is recommended that you check back here occasionally for the latest updates.

For a list of release dates and Sisense's end of support schedule, see Sisense Version Release and Support Schedule.

For information about the Sisense gradual rollout process, as well as an explanation of how the versions and release notes relate to content added during the rollout, see Sisense Gradual Rollout Process.

IMPORTANT NOTE - Regarding Upgrading:

Customers currently running Sisense versions older than L2023.11 cannot directly upgrade to versions L2024.2.0.79 or newer. You must first upgrade your Sisense installation to version L2023.11, or L2024.1, or L2024.2.0.78. Only after completing this intermediate upgrade can you proceed to versions L2024.2.0.79 or newer. This important change is due to Sisense upgrading to MongoDB 6 starting from Sisense version L2024.2.0.79.

Privacy and Security Information

This release contains several security related updates. We highly recommend upgrading to this latest release to take advantage of any security-related updates and benefit from the Sisense support and warranty. In addition, Sisense strongly recommends regularly testing and auditing your environment after upgrading, and periodically during your subscription term, to ensure all privacy and security settings remain in place.

Customers are responsible for controlling and monitoring your environments and are therefore in the best position to ensure the correct security settings are in place for how you use Sisense products.

Due to the complexity of Sisense products, we strongly suggest that all customers ensure that you understand how all of the privacy and security settings within Sisense work.

If you use Sisense to store/process sensitive data, it is your responsibility to review and test your implementation to ensure you are not inadvertently sharing data with unauthorized third parties. For more information on data security rules, see Data Access Security.

BREAKING CHANGES - WARNING!

The following is a cumulative list of potentially breaking changes from approximately the past 12 months, and may also include warnings about upcoming changes:

Connection Management Enablement

Deprecated Internal Endpoints

The following internal endpoints, which were removed from the Swagger API in 2020 but may still be used by some customers, are now deprecated:

/api/internal/connection

/api/internal/connection/{.*}

These legacy endpoints will now return a 410 Gone HTTP error with the following message:

"This connection endpoint has been deprecated and is no longer available. Please use the new Connections Management API endpoints."

Changes to the /api/v2/ecm Endpoint

This endpoint, which is a backend implementation responsible for handling all GraphQL queries, mutations, and subscriptions used by the Sisense Data Tab application, has been updated as follows:

New Optional Properties Added:
name, description, supportedModelTypes, lastModified, and connectionPermissions.

Changed Properties:
provider and parameters are now optional instead of mandatory.

Updates to the /api/v2/datamodels Endpoint

This endpoint will now return the complete connection structure, but all properties, except for oid and provider, will be set to null.

At the same time, /api/v2/datamodel-exports/schema will continue to return connection parameters as before.

Action Required

As Connection Management is now the unified approach for managing data source connections, ensure your custom solutions are updated to use the new /api/v2/connections endpoints.

For more information, refer to the documentation: "API and System Behavior Changes with Connection Management."

Release Overview

Release L2025.2 provides a number of new features, improvements, and fixes to Sisense for Linux.

What's New

The following table lists the high-level impact (or potential impact, if any) of new features, and how to handle it if upgrading to version L2025.2 or newer. Continue reading the Release Notes below the table for a detailed explanation of these features, as well as improvements and fixes.

Feature	Issues and Actions to Consider
Analytical Engine as Default	See Analytical Engine for information about selecting your translation engine.
Image Signature Validation	By default, this feature is disabled. This feature is not supported for offline or air-gapped installations.
Platform Upgrades	N/A
Sisense with Kubernetes using RKE2	Only for on-premise customers who chose to use the Sisense deployment script to deploy and manage your on-premise Kubernetes cluster via the RKE tool.

Analytical Engine as Default

Starting with this version (L2025.2), the Analytical Engine is now the default translation engine for all new data models. The Translation engine is now configurable on a per-model basis, replacing the global setting. Existing models will continue to use the current system-wide translator configuration. A fallback option called “compatibility mode” is available on a per-model basis and it directs the model to fallback to the system’s global translation strategy. The legacy translator will eventually be deprecated in favor of the Analytical Engine.

Benefits of the Analytical Engine include:

Improved accuracy and transparency in data model handling.
Optimized queries for better performance.
More readable queries for user control.
Enhanced capabilities for Live models.
Reduced reliance on many-to-many relationships.
Future support for features like left/outer joins and calculated dimensions.
Ability to use AND/OR filters.

Image Signature Validation

As part of our ongoing efforts to enhance the security and integrity of Sisense, we have introduced this new feature that enables you to validate Sisense images deployed in your environment. This ensures that the images are official, developed, and maintained by Sisense.

By default, this feature is disabled.

Note:

This feature is not supported for offline or air-gapped installations, as the validation process requires access to our official quay.io image repository.

For more information, see Image Signature Validation.

Platform Upgrades

As part of our ongoing commitment to security, performance, and stability, we have implemented the following platform-level updates in this release:

MongoDB Upgrade: Upgraded to MongoDB 6 (Percona distribution) to improve overall database security and performance.

Third-Party Component Updates: Several critical components and services have been upgraded to their latest stable versions, including:
- MongoDB
- RabbitMQ
- ZooKeeper
- FileBrowser
- Ubuntu (base image)
- Alpine Linux (base image)

Framework and Library Enhancements: Numerous internal frameworks and libraries have been updated with minor versions to ensure security hardening and maintain compatibility with modern standards.

These updates help maintain a secure and robust infrastructure, reducing potential exposure to security vulnerabilities and ensuring better performance and long-term supportability.

Sisense with Kubernetes using RKE2

Note:

This topic relates only to on-premise customers who chose to use the Sisense deployment script to deploy and manage your on-premise Kubernetes cluster via the RKE tool.

Rancher Kubernetes Engine (RKE) is a tool developed by Rancher, which is used for deploying and running Kubernetes clusters on your on-premise server(s).

RKE is reaching its End Of Life.

Therefore, Sisense has updated our on-prem deployment process to deploy the Kubernetes cluster using the new RKE2.

The final Sisense version that will install/upgrade Kubernetes using RKE1 is L2025.1.

Subsequent Sisense versions will still be able to deploy over RKE1 (using only update: true and update_k8s_version: false).

However, for new installations for which deploying the Kubernetes cluster via the Sisense deployment code is desired, RKE2 will be installed.

For more information, see:

What's Improved

AI Assistant

If dashboard filters exist in the dashboard, then the dashboard filters are applied by default in the Dashboard AI Assistant. If there are no dashboard filters applied to the dashboard, then the dashboard filters are disabled by default.
AI Smart Matching: The limit for the number of unique values per column has been increased from 100 to 250.
NLG: The NLG is now capable of handling larger datasets. The limit is only based on the LLM input token limitation. When the limit is exceeded, a LlmContextLengthExceedsLimitError occurs.

Connection Management

There is now a centralized view of all connections accessible from the data tab and the same level of experience as from inside of the data model. Therefore, you can now work with a connection without needing to open the data model’s data wizard.

Connectors

Snowflake Key-Pair Authentication: Sisense now supports encryption algorithms for the key-pair authentication method in accordance with Snowflake's latest official requirements (see the Snowflake documentation).

The option "Use modern RSA key encryption" has been added to the new connection wizard and is enabled by default. Clear this option only if you need to use legacy key pairs generated with older encryption algorithms.

Dashboard Co-Authoring

Dashboard co-owners can now change the data source for the shared copy. Co-owners and Designers can change the data source for their private copies. After republishing, the data source(s) will be updated for all private copies (including co-owners' private copies) according to the shared copy data source(s). Widgets created by users in their private copies will keep the original data source.

Data Models & Perspectives

AI Index: From the data model menu, you can now select the columns to be indexed.
Data Model Import: Now, when importing a data model with data security, the system informs about data security rules that will not be imported due to the absence of the users with such emails on the target instance.

FileBrowser

FileBrowser has been upgraded to version 2.32.0.

Narratives

You can now choose which provider to use for Narratives: Arria or SisenseIntelligence.

What's Fixed

AI Assistant

Previously, if the AI Assistant was enabled, a dashboard was published, the AI Assistant was disabled, and the dashboard was republished, the AI Assistant button was still displayed to viewers. This has now been fixed, and when the AI Assistant is disabled, it is not shown to viewers after a republish.

Connection Management

Previously, when changing languages, connections in Connection Management were only partially translated. This has now been fixed, and all static text of the connection flow is translated to the user’s language.

Connectors

The "USE DATABASE" query is no longer executed on each connection to Snowflake. Instead, it is now integrated into the connection string. This change enables more cost-efficient usage.
Databricks: Previously, previewing data in Databricks-based models failed with the following error: "An error occurred while executing request to connector: Parsing failed: [Databricks][JDBCDriver](500051) ERROR processing query/statement”. This has now been fixed and works as expected.
Custom JDBC connectors in environments configured with a reverse proxy are now installed successfully and work as expected. Previously, some endpoints did not account for the proxy configuration, leading to failures.
Previously, when creating XLS connections using "Input Paths of Files or Folder", builds failed with the following error: "Failed to read row: 0, Connector Executing the query on the data source failed". This has now been fixed and works as expected.

Dashboard Co-Authoring

Previously, opening and closing the dashboard sharing dialogue without saving was mistakenly creating a shared dashboard instance. This would lead to losing the subsequent dashboard updates upon the next dashboard sharing. This has now been corrected, such that the shared dashboard is only created after sharing is completed and the dashboard is actually published.
Previously, the ownership transfer via API was not working on dashboards that were not shared with any users. Both endpoints were failing:
- POST /dashboards/{id}/admin/change_owner
- POST /dashboards/{id}/change_owner
This has now been fixed such that the ownership is transferred, and the previous owner is removed from shares.

Note that any operation with dashboard shares publishes a dashboard; this means that the new owner will have shared and private copies.

Previously, co-owners were not able to move their co-owned dashboards into other folders - a dashboard would stay in the original folder for all shared users except, occasionally, the co-owner. This has now been corrected such that placement of a dashboard into another folder is accurately reflected for all users. Note that a co-owner must be the owner of a folder to move a dashboard into it and must republish a dashboard in order to apply the change for shared users.
Previously, enabling and then disabling Dashboard Co-Authoring sometimes resulted in users seeing empty dashboards with no widgets, but only filters present. This has now been fixed and works as expected.

Note that after turning off the feature, each dashboard is assigned an owner from the previous list of co-owners, and the remaining owner keeps their private copy as the owner copy of the dashboard. Any unpublished changes from the dashboard shared modes will be lost; in order to keep the changes, each shared dashboard must be republished before disabling the feature.

Previously, adding rows to a pivot table was not saved after republishing a dashboard. This has now been fixed such that the added rows are saved and rendered as expected both for the dashboard owner/co-owner and the shared users.

Data Sources

Row functions support in the Dtable optimization has been added, which previously, in rare cases, led to incorrect results in Pivot widgets.

Filters

Previously, a default dashboard filter was not properly reset, and was instead replaced with a selection from a widget filter, in the following scenario:
- the filter condition was 'is not',
- the selected filter values were no longer available in the dataset,
- and there existed a widget filter on the same field.
This has been adjusted such that the filter is now reset to 'include all' if none of the selected values are available to the user in the dataset.

Formulas

Formulas now appear correctly in the dashboard editor after being added by the AI Assistant.

Git Integration

Previously, deleting a table or column in a tracked data model was not reflected in the project upon refreshing; it was displayed when another tracked operation was done (e.g., rename table). This has now been fixed and deleting a table or column is reflected in the Git project after sync (i.e., after clicking Refresh).

Installation

Previously, when deploying the latest Sisense Helm chart, there was an issue with volumes being configured twice in the chart. The Warehouse Helm chart configuration has now been fixed.

Simply Ask (NLQ)

Previously, sometimes the data model level Simply Ask context menu was duplicated when switching browser tabs. This has now been fixed and works as expected.

Widgets

Previously, selecting a date that was not available in the dataset on a chart with a continuous timeline resulted in the widget loading endlessly. Additionally, having such a widget in a dashboard prevented exporting the dashboard to PDF. This has been corrected, such that now selecting a missing date on a widget returns no results, as expected.
Previously, when adjusting the zoom bar under charts, the bars and values partially selected by the slider were also partially rendered. This has now been fixed to ensure that all values are displayed fully, including those for which only part of them is selected within the slider.

What's Coming

The following features and improvements are expected to be added soon.

Display Name

Tables and columns in the data models will now differentiate between original, identity, and display names. This will enable data designers to rename tables and columns without affecting their dependent assets, such as widgets or alerts.

Original Name – The physical table/column name in the data source.
Identity Name – The logical name in the data model schema, used as a table/column unique identifier. Changing it will cause existing queries relying on it to fail.
Display Name – The semantic name, used in the application data browser interface (dashboards, data security, drill hierarchies, etc.). Changing it will present an updated name to users interacting with data via the data browser, but will not affect existing assets.

Changes to identity/display names will become effective after building/publishing the model.

Dashboard Co-Authoring - General Availability

Dashboard co-authoring enables sharing the ownership of a dashboard with other users so that multiple co-owners can update and publish a dashboard. It also creates a private copy of a published dashboard for the owners/co-owners, where they can interact with their dashboard as consumers, without affecting the shared version.

Dashboard co-ownership will shortly become available to all customers if enabled by Administrators in the Admin tab > Feature Management page by turning on the Dashboard Co-Authoring toggle. When the feature is enabled, all published dashboards (existing and newly published) will adopt the co-ownership mode.

Report Manager

The Report Manager will now be pre-installed with each deployment which means that you will automatically get the latest compatible add-on version on every Sisense upgrade. As a premium Sisense add-on, it must be enabled in your license in order to actually be enabled in your environment.

Deprecations

Export to Excel - Upcoming Deprecation Notification

This is not yet implemented, but is expected to be added to this version (L2025.2) soon:

Starting from Sisense version L2025.2, all deployments will be automatically switched to the New Export to Excel as their default service for downloading Pivot widgets to Excel. For a short transition period before the next version, it will still be possible to switch back to the legacy exporting service, so that you can adjust and test your integrations that use the exporting API.
Subsequently, by the end of 2025, the previous exporting service will be deprecated. That is, the configuration toggle located in Admin > System Configuration > Exporting > Export to Excel V2 will be removed and the legacy exporting API will no longer be available for use.

You may continue using the legacy endpoint when exporting via REST API until it is deprecated, which will occur by the end of 2025. However, make sure to switch to the new endpoint prior to the deprecation.
- New exporting endpoint to be used:
  
  /api/v1/export/jaql/xlsx

Filters - Upcoming Deprecation Notification

This is not yet implemented, but is expected to be added to this version (L2025.2) soon:

Starting from Sisense version L2025.2, all deployments will be automatically switched to use the default filters editor. For a limited time, it will still be possible to switch back to the legacy dashboard and widget filters, so that you can verify that the existing filters are not affected and make adjustments if necessary.
Subsequently, by the end of 2025, the legacy filters editor will be deprecated, and the configuration toggles Date/Time Filters, Numeric Filters, and Textual Filters located in Admin > Feature Management will be removed.