L2025.3 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 L2025.2.0.249 cannot directly upgrade to versions L2025.3 or newer. You must first upgrade your Sisense installation to version L2025.2.0.249 or L2025.2.0.496. Only after completing this intermediate upgrade can you proceed to version L2025.3 or newer.

This important change is due to Sisense upgrading to MongoDB 8 starting from Sisense version L2025.3.

  • To download the latest Sisense version, or to upgrade to an older version, see that version’s Release Notes and contact your Sisense Customer Success Manager for the version package.

  • To upgrade to this version of Sisense:

    • Read the Release Notes of all the versions following your current version, up to and including the version to which you are upgrading.

    • Run a system backup before upgrading. See Backing up and Restoring Sisense.

    • Follow the upgrade procedure in Upgrading Sisense.

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:

API Token must be switched on in Feature Management > User Profile in order for the apiToken endpoint /api/v1/authentication/tokens/api/renew to return a JWT result as it previously had. If this feature toggle is off, a 403 Forbidden error will be returned instead.

Ceph is no longer supported as a shared storage layer. Migrate to supported alternatives, such as FSx (for AWS) or NFS (for non-AWS) to ensure continued compatibility.

Sisense automated system emails have been updated to match the new Sisense branding. As a result of this change, custom modification to the system emails will be overridden upon upgrade in case you have modified the contents of default email templates, but have not replaced the Sisense logo with your own logo image.

The default email templates are .less and .ejs files stored in the /opt/sisense/storage/emails folder OR in the /emails folder in the File Manager.

Make sure to back up your customized email templates before installing an upgrade so that you can restore them afterwards.

In order to prevent the need to restore your changes for future upgrades, store the customized templates in the dedicated branding folder (/opt/sisense/storage/branding/<yourbrand>/emails) and configure Sisense to send them instead of the original Sisense automated emails as described here. This functionality is only available if White Labeling is enabled in your license.

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.3 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.3 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
Compose SDK Mode (Beta) Compose SDK Mode is currently in Beta. Note the Known Issues in the documentation.
Display Name Display Name is currently in Beta. Note the Known Issues.
ElastiCube Cloud The ElastiCube Cloud option should currently be considered by new users with small to mid-scale data usage, up to 80 GB. However, there is no concern of outgrowing this solution - while the initial limit will be 80GB, this will increase over time to meet any required size.
Infra

  • MongoDB has been upgraded to version 8. See Important Note above concerning upgrading Sisense.

  • Added support for upgrading RKE and Kubernetes to version 1.33. Kubernetes is not upgraded by default during this update. To enable the upgrade, set the following parameter in your values.yaml file - update_k8s_version: true

Semantic Enrichment

See the Note below, and more information in the documentation.

Sidebar Navigation

N/A

Compose SDK Mode (Beta)

Compose SDK Mode is a powerful new dashboard feature designed to streamline embedding Sisense with Compose SDK.

  • Renders dashboards in Sisense Fusion using Compose SDK for an accurate preview.

  • Identifies compatibility issues and prevents incompatible modifications.

  • Facilitates adaptation of existing dashboards to embedding with Compose SDK and creation of new, natively compliant dashboards.

Use Compose SDK Mode to build and embed better dashboards.

Display Name

Tables and columns in the data models will now differentiate between original, identity, and display names if enabled by an Administrator in the Admin tab > Feature Management page by turning on the Display Name toggle. This allows 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 customizable alias to be displayed in dashboards. Changing it will present an updated name to users in the Analytics page, but will not affect existing assets.

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

Known Issues

  • When searching for a table/column inside the data browser on the Analytics page, the search returns results based on both identity and display names.

  • Metadata Aliasing – Search inside the data browser on the Analytics page returns the Identity name instead of the Display name when both the display name and metadata aliasing are applied.

  • Smart field suggestions (both field names and table names) are not updated after publishing a live model. This functionality works correctly for ElastiCubes. Workaround: Manually trigger the POST suggestion/refresh API.

ElastiCube Cloud

ElastiCube Cloud is a modern, managed analytics solution. It represents a focused, scalable step toward the broader vision of a fully managed data warehouse (MDWH), while delivering immediate performance improvements and easier deployment. ElastiCube Cloud allows data modelers to use the Sisense cloud as a destination for their ElastiCubes. As this is managed on the Sisense cloud, there are no infrastructure and operation burdens on customers.

Infra

  • MongoDB has been upgraded to version 8.

  • Added support for upgrading RKE and Kubernetes to version 1.33.

    Note:

    Kubernetes is not upgraded by default during this update. To enable the upgrade, set the following parameter in your values.yaml file - update_k8s_version: true

Semantic Enrichment

Semantic Enrichment is a new feature that enables you to use Sisense Intelligence to automatically provide descriptions for your data models’ tables and columns. This assists data administrators in creating clear and informative text that can be utilized by both humans and the Sisense Intelligence assistant. The primary purpose of the enrichment is to enable the assistant to better understand the models and to improve the answers provided. The descriptions will cover key aspects of the data, such as its nature, its usage, optional formatting for textual IDs, and a summary of the data's time granularity and attributes.

  1. In the Data tab, for the relevant data model, click > Semantic Enrichment.

  2. If the Semantic Enrichment confirmation and note window is displayed, click Enrich Semantics.

    The Description fields (not including hidden tables/columns) are updated with the Semantic Enrichment automatically generated descriptions. Those descriptions are marked with the Sisense Intelligence icon .

Note:

  • This feature is currently off by default and can be enabled by an administrator in the Sisense Intelligence settings.

  • This feature requires you to set up your own Large Language Models.

  • Manually added/edited descriptions are not overridden by the Semantic Enrichment generated descriptions.

  • The generated descriptions can be manually edited.

Sidebar Navigation

The top navigation bar, including all the tabs and icons can now be moved to the sidebar. This feature is currently off by default. In order to use Sidebar Navigation, it must be enabled by an Admin, in the Admin tab, under App Configuration > Feature Management in the Management section.

What's Improved

Assistant

  • Recommended questions in the assistant have been improved:

    • The assistant now suggests a wider variety of questions for deeper exploration.

    • The underlying API also supports a userPrompt field, allowing tailored instructions for more relevant recommendations.

      GET /ai/recommendations/query/{sourceId}/{numOfRecommendations}

Narrative

  • Widget narratives powered by Generative AI (Cloud only) have been improved. Cloud customers with the Narrative NLP package now get more insightful narratives using Generative AI. The previous version remains available for a limited time.

User Parameters

What's Fixed

Assistant

  • An issue has been fixed where chart labels did not appear properly with multiple break-bys. The assistant has been improved to render labels on charts that include more than one break-by field for clearer and more accurate visuals.

  • Stability improvements have been implemented for the Studio Assistant (Public Preview). Issues have been fixed for chart rendering, editing, missing data models, and model config updates to improve overall reliability.

Connectors

  • Data source connection to MongoDB with the "Use Svr Connection" option is now working as expected. Previously, it failed with the following error: "Connection failed: Authentication."

Filters

  • Previously, changing dashboard filter selection by an administrator in /adminAccess mode resulted in converting a multi-select filter into a single-select. This has now been fixed and works as expected.

  • In some earlier versions, the blank/empty string values were not processed correctly in the legacy filter editor, being displayed as {“data“:””,”text”:””}. This has now been fixed, so that empty strings are presented as "(blank)" in the filters UI.

Forecast and Trend

  • An issue has been fixed where special characters caused “Analyze It” trends to fail. A problem was resolved where values containing special characters (such as “&”) prevented trend analysis from working correctly in the assistant.

Git Integration

Widgets

  • Previously, removing a value from a chart by clicking on the corresponding legend item did not remove its total value label. This has now been corrected such that when a value is removed, the related labels are removed as well.

  • Previously, sorting date-time values from a Table widget column header was not applied correctly and instead resulted in a 'no sort' order. This has now been fixed, so that clicking on a Table column header sorts the values in ascending/descending order as expected.

  • Previously, bar chart height was not always recalculated correctly after applying filters, leading to displaying the bars poorly laid-out tightly together at the top of the widget. This has now been fixed, ensuring that the bars are evenly spread across the chart area after a dashboard filter was applied.

  • Previously, the scatter map did not return any results if empty strings were present in the data model and included in the query (e.g., due to applying filters). This has now been corrected by excluding the blank values from map queries to prevent them from breaking.

  • Previously, the sorting order of blocks representing values in the treemap widget was broken after changing the window size. This has now been fixed to maintain the correct sorting order of the values.

  • Previously, long category titles in bar charts were not always truncated, affecting the chart display and readability. This has now been fixed to ensure that category titles do not obscure the chart area.

  • Previously, clicking “Clear Selection” on a Pivot widget would sometimes reset the corresponding dashboard filter, without updating the widget itself. This has now been corrected to ensure that the selection in the widget is cleared as expected.