Previously, when a "Break by" field in a line chart contained null or empty value, the chart rendered completely empty and affected relevant dashboards. This has now been fixed, and line charts no longer render empty if a "Break by" field contains a null or empty value.

Previously, when using JTD from a widget with a break-by and specific filter relationship settings, the JTD action failed. This has been fixed and the target dashboard now opens as expected.

Previously, when applying filter changes to a JTD drill dashboard, Accordion dashboards did not reflect those changes when the dashboard was accessed using a Web Access Token (WAT). This has been fixed and the Accordion dashboards reflect the changes to the dashboard filters.

Previously, if a dashboard contained an ampersand (&) in its name, Accordion could not open the dashboard when referenced by name. This has been fixed and Accordion can successfully open a target dashboard containing an ampersand in its name.

Previously, calculated dimensions that started and ended with a constant string (e.g., CONCAT('n',[Name], 'L')) sometimes returned an error when applying a filter on it. This has now been fixed, and applying a filter on this type of calculated dimension works as expected.

Previously, when exporting a large dataset (> 1000 rows) as an Excel spreadsheet, an extra subtotal row was inserted every 1000 rows. This has been fixed and subtotal rows are only generated for the actual subsets, matching the pivot data displayed in the dashboard.

Previously when opening the legacy date filter, the filter menu was blank, and users could not choose a different time-based filter. This has now been fixed, and the menu appears as expected.

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.

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

Dashboards now open in Shared mode by default, featuring an improved notification that allows co-owners to easily switch to Private mode or return to the Analytics page if the shared version is currently locked for editing by another user.

When a user activates Private mode, a notification appears at bottom of the dashboard to indicate you are in private mode. Additionally, a broken line outlines the entire dashboard for visual confirmation.

When dragging and dropping a widget into a co-owned dashboard from another dashboard, the widget is added to the shared copy. If the shared version is locked, the widget can still be added to the private copy.

Previously, when the main dashboard owner of a co-owned dashboard was deactivated, other co-owners were unable to access and edit the dashboard. This has now been fixed, and dashboards can be accessed by co-owners even if the main owner has been deactivated.

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.