2026.2 Release Notes

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.

Versions Documented in these Release Notes

IMPORTANT NOTES

Regarding Salesforce Security Updates to the "Use Any API Client" Permission:

Regarding Upgrading:

  • Version L2025.4 Service Pack 1 contains an important fix. Therefore, it is strongly recommended to upgrade to SP1 or newer.

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

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:

2026.2.0 Release Overview

Release 2026.2.0 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 2026.2.0 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

NLQ Assistant – Natural Analytical Responses (Preview)

 

Sisense Intelligence with Credits

 

Unified Narrative Administration

 

NLQ Assistant – Natural Analytical Responses (Preview)

The Sisense assistant now answers analytical questions with natural-language responses that include exact data values and concise insights, while continuing to generate the relevant visualization.

  • Natural-language analytical answers – Quantitative questions now return direct answers with exact values plus a focused insight (for example: trend, ranking, or share of total).

  • Question-aware responses – The assistant adapts responses by query type, including:

    • Quantitative – direct answer + insight

    • Creation requests – creates the requested visualization and confirms the action with a brief insight

    • Comparison – includes values, deltas, and percentages

    • Metadata / structural – returns text-only field or definition information

    • Ambiguous questions – asks clarifying follow-up questions with suggested options

    • Forecasting / trends – summarizes projected direction alongside the visualization

    • No data found – returns a clear text explanation without showing an empty visualization

  • Shared filter context – Assistant responses and generated charts now respect active dashboard filters, ensuring consistent results across dashboards, NLQ, and assistant interactions.

Preview Scope

This release covers natural-language responses for core analytical question types and filter synchronization. Governance controls and complex explanatory “why” questions remain out of scope for this phase.

Sisense Intelligence with Credits

Sisense Intelligence with Credits is now GA. This update removes the complexity of managing large language models and replaces technical metrics with a predictable, user-friendly consumption model.

Previously, tracking AI usage meant dealing with "tokens", a metric that makes sense to a machine but is difficult for users to budget against. We have introduced a Credit Abstraction Layer that translates internal token usage into fixed, easy-to-understand AI credits.

Whether you are using the AI Assistant, generating Narratives, or performing Semantic Enrichment, every action now has a clear cost in credits. In the future, more capabilities, other than AI, will be included under Sisense credits.

Key Benefits

  • Zero Setup, Infinite Value: Managed LLM is powered by Azure OpenAI and fully managed by Sisense. You get enterprise-grade security and data privacy without the maintenance.

  • Always the Latest: No more manual upgrades. Managed LLM customers are automatically connected to the latest, most powerful models.

  • Predictable Pricing: By mapping feature actions to fixed credits, you’ll know exactly how far your monthly allotment will take you.

  • End-to-End Governance: Centralized logging ensures both internal token costs and external credit consumption are tracked accurately for total transparency.

Real-Time Visibility & Quota Management

For administrators, staying in control of consumption is now easier with built-in monitoring tools:

  • Real-Time Dashboard: View credit consumption across your organization as it happens.

  • Proactive Alerts: To prevent a sudden "feature blackout," the system triggers automated notifications when your organization reaches 85% and 100% of its credit quota.

  • Monthly Refreshes: Credits refresh every month based on your subscription, ensuring your team has a consistent pool of resources.

Flexible Subscription Tiers

To match varying organizational needs, we offer various subscription tiers. These tiers provide different levels of credit allotments, allowing you to choose the volume that best fits your AI usage patterns.

Note:

While we continue to support "Bring Your Own LLM" configurations, AI Credits and the associated managed benefits apply exclusively to the Sisense Managed LLM service (i.e., they are only available for our managed cloud customers).

While you can still bring your own model, the Managed LLM is the fastest path from purchase to value. It eliminates the "setup tax," provides superior support since Sisense owns the end-to-end experience, and ensures your AI capabilities are always-on and always-optimized.

Unified Narrative Administration

All narrative-generation capabilities have been consolidated under a single Narrative setting, giving admins a clear, consistent way to control and monitor narrative usage across the product.

A single Narrative toggle in Sisense Intelligence Admin now controls:

  • Dashboard/widget Narratives

  • Narrative API usage (unified narrative REST API)

Cloud Linked Features Dependency

If Cloud Linked Features (CLF) is OFF, Narratives are disabled, even if the Narrative toggle is ON or covered by license. In this case, users see a notification indicating that Cloud Linked Features must be enabled for Narratives (and other AI capabilities) to work. This applies to:

  • Dashboard/widget narratives

  • Assistant-generated narratives

  • Narrative API calls

Admin Impact and Configuration

To enable Narratives, ensure:

  • Cloud Linked Features is turned ON, and

  • Narrative is enabled under Sisense Intelligence > Feature Management.

Disabling the Narrative toggle:

  • Hides or disables the Generate Narrative button in the Assistant.

  • Disables narrative generation in dashboards/widgets and via the narrative API.

What's Improved

Analytical Engine

APIs

There is a new endpoint for partially publishing semantics:

PATCH /api/v2/perspectives/{perspectiveOid}/publish-semantics/partial?fields=<comma-separated field paths>

This endpoint allows updating specific semantic properties (e.g., only customTranslationMode) without publishing other pending draft semantic changes.

Compose SDK Mode

  • Compose SDK Mode now supports embedding code at the widget level.

Outer Joins (GA)

Outer Joins are now General Availability (GA).

Sisense Intelligence

  • When using the assistant with Azure GPT 4.1, chart generation speed has been improved.

  • The assistant now supports shared formulas.

WAT

  • The URL length for the Jump to Dashboard in the WAT flow has been optimized by adding a mechanism to compress the 'filter' parameter in the URL. This reduces the number of cases where the URL is too large for the nginx server to process. (In some cases, it may be necessary to adjust the nginx server default parameters).

What's Fixed

Access Control

  • Tightened access control for the /storage/fs/validate_file endpoint so that only users with permission to upload data sources (Data Designer and higher roles) can access it; lower-privilege roles now correctly receive HTTP 403.

Add-ons

  • Previously, when using JTD, increasing the popup window size to 130% or larger sometimes caused the popup to be truncated, cutting off the dashboard header, navigation buttons, and scrollbar. This has now been fixed, and navigation buttons, windows, and menu bars remain visible in JTD popup windows, even when resized above 130%.

  • Fixed an issue where enabling or disabling add‑ons (plugins) on self‑hosted Sisense deployments running with a non‑default Linux user ID (non‑UID 1000) could fail with a Permission denied (EACCES) error on licensed plugin files (for example, licensed-plugins/<plugin>/plugin.json). As a result, plugin state changes (enable/disable) appeared to revert and could not be applied.

    File ownership for licensed plugin files is now aligned with the configured deployment UID (securityContext runAsUser/fsGroup), so plugin state changes work as expected on deployments using custom UIDs.

  • Fixed an issue in the SmartShare add-on where sharing dashboards with a very large number of users or groups could cause timeouts and 500 errors. The add-on now processes these requests in smaller batches, ensuring reliability and responsiveness even when managing extensive sharing lists.

APIs

  • Previously, updating data security rules via REST API 1.0 PUT /elasticubes/live/datasecurity/{dataSecurityId} stored the partyId as a string instead of an ObjectId. This caused data integrity issues and could break downstream processes expecting the correct data type. The API now correctly stores partyId as an ObjectId.

  • Previously, the PDF preview layout was not saved if the dashboard contained a widget added via POST /api/v1/dashboards/${dashboardId}/widgets/. The issue only occurred via API, not if the widget was added using the UI. This has now been fixed, and the PDF preview layout is saved when using the API as well.

  • Previously, the analyticalEngine field and AE_MODE settings were ignored when creating or updating data models via the /v2/datamodels REST API. You can now successfully configure and retrieve Analytical Engine settings via the API.

Compose SDK Mode

  • Previously, in Compose SDK Mode, Download Image and Edit script menu items were shown even though they are not supported. These options are now hidden to prevent confusion; standard mode remains unchanged.

Data Models

  • Previously, importing or exporting models with a high number of Data Security rules (~2,700+) caused a pod to crash. This was due to the system attempting to encrypt each security rule member individually, leading to TCP port exhaustion and a loss of connectivity for critical services. The encryption logic in the model import/export flow has been refactored to use a bulk encryption API with chunking (processing items in batches of up to 200). This dramatically reduces the number of concurrent HTTP requests, preventing port exhaustion and ensuring stability during large model operations.

  • Previously, the Analytical Engine setting was not preserved when duplicating a data model and was missing from the data model APIs. This has now been fixed and works as expected.

Data Security

  • Previously, importing a model with many DS rules sometimes silently skipped data security with no error displayed (import completed "successfully", without Data Security). This has now been fixed, and Data Security is applied as expected.

Export to PNG

  • Previously the user profile language was used for dashboard PNG exports, ignoring the lang URL parameter. This has now been fixed and PNG exports respect the lang URL parameter.

Export to PDF

  • After adding support for word wrap in rows, the wordWrapRows option now affects the exported PDF output in the same way as it does in the table preview. When enabled, each row may span multiple lines, reducing the number of rows rendered per page. As a result, the total number of pages in the exported file may increase compared to exports without word wrapping. Based on internal measurements, memory consumption in the exporting pod may increase by approximately 20% under these conditions. In environments with large datasets, this may lead to export failures due to insufficient pod memory limits. If export errors occur after enabling word wrap, consider increasing the limits.memory setting for the exporting pod. If issues persist, please contact Sisense Support.

  • Previously, exporting a dashboard to PDF resulted in outdated or incorrect data when the metadata translations plugin was enabled. This occurred because certain BloX widget actions (such as Dimension Swapper) triggered a recursive loop in the metadata processing, preventing the dashboard from saving recent changes before the export. This has now been fixed by implementing cycle detection to ensure dashboard updates complete successfully, allowing the PDF export to reflect the most current data and translations.

Filters

  • Previously, selecting N/A plus other values in a widget sometimes caused expanded filters to display incorrect results. This has been fixed and filters work as expected.

  • Previously, charts such as bar charts or column charts could not be filtered by the columns/bars with the following condition: Days granularity in the categories and Days in Date dashboard filters. This has been fixed and interactive filtering now works as expected.

Git

  • Previously, in some cases, syncing dashboards via Git that contain rich text widgets, Git showed uncommitted changes even when no edits were made. This has been fixed and Git only shows actual uncommitted changes.

  • Previously, in some cases, the commit author's email address was sent to remote repositories in a URL-encoded format (e.g., `user%40example.com`), causing validation failures. The email addresses are now correctly decoded before being sent, ensuring successful pushes even to repositories with strict email format requirements.

Outer Joins

  • Previously, applying an include filter to show only specific members would still return unexpected NULL entries in the results. This occurred in data models that use a combination of outer and inner joins between tables, where the filtered field was connected through multiple levels of joins. This has been fixed and queries now correctly exclude NULL entries and return only the filtered members.

  • Previously, when using Outer Join with Redshift, queries sometimes failed with a "column reference is ambiguous" database error. This occurred when the query included columns from different tables that had the same name but different casing (e.g., Country_id and country_id). This issue has been resolved and columns with identical names but different casing are properly disambiguated.

  • With this fix, perspectives now correctly persist and apply the join type from the root model, ensuring LEFT JOIN behavior is honored in both the UI and the underlying queries, and eliminating the need to manually re‑define join types in each perspective.

  • Previously, in ElastiCube models, filtering for NULLs on the null-producing side of an outer join resulted in zero rows. This has been fixed and the underlying SQL takes into account NULL values produced by the outer join as well as NULL values in the original tables.

  • Previously, when applying a top or bottom ranking filter on a dimension that uses an outer join, rows where the dimension value is N/A were incorrectly excluded from the results. This issue has been resolved and N/A dimension values are now correctly included in Top/Bottom ranking results when using outer joins.

Perspectives

  • Previously, in the Sisense semantic model, perspectives did not always correctly inherit LEFT JOIN relationships defined in the root model. In some cases, joins that were configured and displayed as LEFT JOIN in the UI were executed as INNER JOIN in the generated SQL for perspective‑based widgets, causing inconsistent and inaccurate results. This has been fixed and Perspectives apply the join type from the root model, ensuring LEFT JOINs execute as expected.

Report Manager

  • Previously, in some cases, when exporting a report from Report Manager in a live model, the export failed due to a broken retry mechanism. This has been fixed by modifying the retry behavior for report exports.

  • Previously, in some cases, scheduled emails sent by Report Manager to external recipients failed with a vague error description in the UI that could not be used to troubleshoot. This has been fixed and the UI now displays a clear error message.

  • Previously, in some cases, Report Manager UI indicated a scheduled report was sent even though some recipients did not receive the report. This has been fixed and the UI now accurately reflects actual report delivery.

  • Previously, when performing a search in the left navigation panel, the UI occasionally froze for up to 10 seconds. This has been fixed by moving search functionality to the server, which subsequently frees up client resources.

Single Sign On (SSO)

  • Previously, users were sometimes unable to authenticate via SSO due to a malformed redirect URL (//openid) caused by the browser’s cache. This has been fixed by correcting the way URLs are constructed, thereby resolving failed logins without requiring users to clear their browser cache.

Sisense Intelligence

  • Previously, when the assistant generated a new visual or metric, you could only see the updated/new visual by clicking outside of the popup window and reopening the assistant. This has been fixed, and the visual is now updated in the existing widget.

  • Previously, it was not possible to scroll through the list of created charts in the assistant when the list exceeded the window height. Vertical scrolling has now been added to ensure all charts remain accessible.

User Parameters

  • Previously, when an admin manually created a user with an email address that contained an invisible (non-printing) character and the same user logged in via SSO without using the invisible character, Sisense treated them as 2 separate accounts. This led to duplicate accounts that appeared to have the same email address, causing issues with dashboard access and permissions. This has now been fixed by adding validation that blocks the use of email addresses containing invisible characters both in the Sisense UI and in the backend.

Widgets

  • Previously, in Pivot2 widgets, null values were sometimes displayed as 0 instead of N/A after changing the number of decimal places displayed in a column, leading to null values being interpreted as actual data. This has been fixed and Pivot2 widgets display null values as N/A.

  • Previously, in pivot widgets with many columns, the end of the last column was occasionally cut off, making the resizing handles and sorting button inaccessible. This has been fixed by updating the widget UI and scrolling logic so that all columns and buttons are visible regardless of the number of columns.

  • Previously, when clicking cancel while a widget is loading, the widget’s toolbar disappears and users cannot open or edit the widget. This has been fixed and the toolbar no longer disappears.

  • Previously, Pivot widgets with outer joins encountered a query error after an upgrade if joined tables contained columns with identical names. This has been fixed and Pivot widgets now function correctly, even when joined tables share column names.

  • Previously, in some cases, the scroll bar was hidden in table widgets with many columns, preventing users from scrolling through the table. This has now been fixed, and the scroll bar appears as expected regardless of screen resolution.

Deprecations

  • Nginx ingress is being deprecated. It is being replaced with Nginx Gateway Fabric (NGF).

  • The following old Narration endpoints are being deprecated:

    • /ai/nlg/queryResult

    • /ai/describe/query

2026.2.1 Release Overview

Cloud Availability

This release is currently only available to cloud customers. It will be released shortly for on-premise availability as well.

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

The content below describes the new features, improvements, and bug fixes included in the May 2026, 2026.2.1 release.

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.

What’s New

CSDK Rendering in Widget Editor

You can now create and edit CSDK-based widgets directly in the Widget Editor when working in CSDK mode:

  • CSDK chart add-ons (including those supported out of the box by CSDK) are rendered using CSDK inside the editor

    • Dashboard creators can see and refine their custom visualizations as they build.

  • Existing editing panels and modals remain unchanged,

    • Provides a familiar editing experience

    • Full support for CSDK widgets in CSDK-mode dashboards.

What’s Improved

Calculated Dimensions (GA)

  • Calculated Dimensions were added in version 2026.1.1 as beta. They included string manipulation functions - “Left”, “Right”, and “Concat”. With version 2026.2.1 Calculated Dimensions are now General Availability (GA), and include string comparison functions as well - “Case When”, and “If”. As before, these functions are run directly within the widget editor, without requiring backend data modeling changes or ElastiCube rebuilds. See the Dashboard Functions Reference for syntax, examples, and limitations.

Compose SDK Mode

  • In Compose SDK mode, widget previews in the widget editor are now rendered with Compose SDK, ensuring a more consistent experience when designing, configuring, and embedding widgets.

Connectors

  • The Snowflake JDBC connector has been upgraded to version 3.27.1.

Dashboard Co-Authoring

  • When a user is editing a shared dashboard, the dashboard is locked for other owners. The dashboard remains locked until the user releases it or the inactivity timeout duration is reached. The timeout period can be set to between 1 hour and 1 year.

Sisense Intelligence

  • NLQ Assistant – Natural Analytical Responses (GA) - The assistant’s natural analytical responses feature is now GA, making it available to all customers. This release still covers natural-language responses for core analytical question types and filter synchronization. Governance controls and complex explanatory “why” questions are not yet implemented.

  • Transparent answers with visible query logic in the assistant - A query definition sentence that describes the underlying analytical query in plain language is now displayed in widgets in the assistant canvas. For example, a query definition displayed might be: Total Sales by Product in April 2026.

    • Each widget automatically generates a concise natural-language summary of its query, covering key elements such as measures, breakdowns, and filters.

    • The query definition is displayed directly in the canvas UI alongside the widget, so you can understand what a visualization represents at a glance.

    • You can hover over a query result to display a tooltip with info such as table and formula data.

    This means that you now have transparency, seeing how the assistant understands what you ask and if that understanding is correct.

    Scope:

    • This initial release is display-only; interactive editing of the query definition will be addressed in a future version.

    • In a future version, the definition will stay in sync with the widget and update automatically when the query changes.

  • Assistant/Narrative button - A dedicated Generate Narrative button has been added to the top banner of the assistant canvas interface, making narrative capabilities easily discoverable without leaving the assistant workflow. This button provides a direct entry point for narrative generation within the assistant, ensuring consistent behavior, governance, and credit attribution across all Narrative surfaces.

    The button's visibility is dynamically controlled by the global Narrative system toggle. When Narratives are disabled at the system level, the button is automatically hidden for all users across all entry points, including the assistant.

    Usage triggered via the Assistant Narrative button is now correctly tagged as "narrative" (or "narrative-no-limit") for billing and telemetry purposes. This ensures that narrative actions consume Sisense credits according to narrative entitlement logic, rather than being attributed to general assistant usage. For users without a Narrative license, the button integrates with the credit management framework, enabling credit-based deduction for narrative generation.

    If Cloud Linked Features (CLF) is OFF, Narratives are disabled, even if the Narrative toggle is ON or covered by license. This applies to assistant-generated narratives as well.

  • Quota Notification Enabled by Default - The Sisense Intelligence usage quota notification is now enabled by default for all users. When you reach 85% of your monthly credit quota, you will automatically receive a warning notification; there is no manual configuration required.

    In a future release, administrators will retain the ability to disable this notification via a toggle on the Credit Usage page under Admin Settings. The 100% quota limit notification (indicating Sisense Intelligence responses are temporarily unavailable) remains always-on for all users.

Two-Factor Authentication (GA)

What's Fixed

Add-Ons

  • Previously, when using add-ons in Compose SDK mode, Sisense sometimes displayed an incorrect warning message that the add-ons were not recognized. This has been fixed and add-ons no longer trigger false warnings.

  • Column Level Security - Previously, when the Column Level Security add-on was activated, users were sometimes unable to see or access the full list of available fields in the “Add Data” and “Add Filter” menus. This has been fixed and the field picker now automatically fetches additional fields until the list is populated or all results are retrieved.

APIs

  • Previously, when users attempted to add a column description via REST API (PATCH) the descriptions did not persist once the page was reloaded and only appeared after the schema was updated manually. This has now been fixed and the column descriptions added via an API call are saved.

Assistant

  • Previously, the assistant in dashboards generated excessively large prompts, causing users to exceed their token-per-minute (TPM) quota and encounter HTTP 429 errors. The prompt generation logic has been updated to ensure prompts remain within expected limits, providing consistent performance and preventing unexpected service interruptions.

Calculated Dimensions

  • Previously, Calculated Dimensions using `CASE WHEN` formulas could fail in specific cases with a "column does not exist" error. This occurred in single-table queries because certain required dimension tables were incorrectly excluded from the SQL join logic. This has now been fixed such that all tables referenced within a `CASE` expression are correctly identified and joined, resulting in accurate query execution.

  • Previously, Calculated Dimensions using a `CASE WHEN` formula with only a `NOT` condition failed to load, resulting in a "Failed to find underline column" error. This fix ensures that the system correctly identifies the underlying data columns when a `NOT` operator is used as the primary condition in a case statement.

Connectors

  • Previously, the Microsoft SQL Server connector occasionally failed to establish a connection with older versions of SQL Server (such as SQL Server 2014) due to a Java update that disabled legacy TLS_RSA cipher suites. This fix introduces a new environment variable, SISENSE_ENABLE_LEGACY_TLS, allowing users to explicitly re-enable support for these legacy ciphers when necessary. Additionally, the fix ensures the connector correctly respects the "Encrypt Connection" setting in the UI.

Dashboards

  • Previously, after saving changes in the CSDK widget editor, the relevant dashboard briefly displayed outdated data. This has been fixed and dashboards display updated widget data without having to reload the dashboard.

Data Models

  • Previously, in some cases, the Discard Pending Changes button in the data model tab failed to revert the data model to its previous state. This has been fixed and the button now acts as expected.

Filters

  • Previously, applying combined date and time filters on MySQL live models caused widget errors or inconsistent results. This was due to failures in query generation, such as unresolved column aliases in compatibility mode or incorrect parsing of time formulas in Analytical Engine mode. This has been fixed and SQL queries are correctly generated and validated for simultaneous date and time filtering.

Licenses

  • Previously, there was an issue where user license counts (Admins, Designers, and Viewers) were displayed incorrectly due to double-counting across multiple tenants. This has now been fixed to ensure accurate license utilization reporting and to prevent the display of negative "remaining" counts in the user interface.

Outer Joins

  • Previously, when multiple filters were applied to tables connected by an outer join, widgets would occasionally fail with an "Internal Analytical Engine Error". This has been fixed and the original join methods and field aliases are correctly preserved, ensuring filters work as expected.

Pivot Tables

  • Previously, pivot tables failed to calculate correct grand totals and subtotals when combining Distinct Totals with past interval quick functions (such as growth or difference). This has been fixed and pivot tables now handle past interval quick functions correctly.

  • Previously, pivot tables occasionally hung if the WebSocket connection was interrupted (e.g., network drop or load balancer timeout). The pivot client now automatically detects a reconnection and resends the request with a new query ID, ensuring the data loads correctly without requiring a manual page refresh.

Report Manager

  • Previously, when sending reports to non-system tenants, Report Manager sometimes sent scheduled emails without the Excel/CSV attachments (pivot/table widgets). This has been fixed and Excel/CSV exports work as expected for non-system tenants.

Widgets

  • Previously, grouping by “Every Second” or rounding to the nearest 15/30 minute intervals in a date column in MSSQL Live Cubes, caused query and widget errors. This has been fixed and time-based grouping and rounding options work correctly in MSSQL Live Cubes.

Deprecations

  • The legacy Excel exporting service is no longer available starting from Sisense version 2026.2.1. You must switch to the new endpoint, /api/v1/export/jaql/xlsx, prior to upgrading to 2026.2.1 or newer.

  • Quest is no longer supported starting from Sisense version 2026.2.1.