Date: 9 January 2026
New export dashboard capabilities
Two new dashboard export capabilities are available. You can export the entire dashboard to Excel or send the dashboard via email.
Export whole dashboard to Excel
You can export an entire dashboard tab, including the underlying data from each dashlet, to a multi-tabbed Microsoft Excel file.
When viewing a dashboard tab, select to generate the export.
You can specify how much data to include from each dashlet:
- All data
- A limited number of rows
The resulting Excel file contains a first tab with a PNG image of the entire dashboard, followed by individual tabs for each dashlet's data.
Send dashboards via email with supporting data
You can email entire dashboards directly from Data360 DQ+ to users or environment groups.
When viewing a dashboard tab, select from the toolbar.
In the compose window, enter the following:
- email title
- body text
- recipients
You can choose environment groups or individual users, and the system automatically removes duplicate recipients across selected groups.
Inline expression editing across multiple components
Expression editing has been improved to allow direct, inline changes without opening a separate dialog wherever multi-line expression fields were previously read-only. This enhancement applies not only to Analysis nodes but also to other components across the platform.
- Analysis nodes
- Filter node expressions
- Compute node expressions
- Group By aggregation expressions
- Completeness Check expressions
- Consistency Check expressions
- Recon Check match conditions and expressions
- Uniqueness Check match expressions
- Process Model definitions
- Data View definitions
- Case and Data Store definitions
- Rule Library
This enhancement reduces the number of dialogs you need to open and enables faster expression changes, with real-time validation feedback as you type.
Filter and read single files in Azure Storage
Azure Data Lake Storage (ADLS) data stores now support filtering and reading at the individual file level, in addition to the default folder-level behavior.
A new Target Path Type option lets you choose between the following modes:
- Folder (default)
- File
When you select File, the regular expression filter is applied to file names, allowing you to create separate data stores for different file types in the same folder, each with its own layout.
Use File mode when you need different layouts for different file types that are stored in the same folder.
Create environment from previous version settings
You can create a new environment by importing environment settings that you previously downloaded.
Go to and select + New Environment.
A dropdown menu appears, where you can choose one of the following options:
- Create a new environment from scratch.
- Import an environment from a saved configuration file.
When you import a configuration file, the system automatically converts all encrypted values to the correct encryption format for the target installation or tenant realm.
The Root Asset in the Govern tab is reset so the new environment has its own asset hierarchy. This lets you reuse existing configurations while ensuring each environment remains independent, and helps you quickly replicate environment setups across different installations.
Other changes
Infrastructure updates
The following infrastructure components have been updated to support the latest execution engine requirements:
- Upgraded Azure Databricks to version 16.4.x-scala2.12 to meet the latest execution engine requirements.
- Updated AWS EMR to version 7.9.0 in the infrastructure creation scripts to support the latest execution engine.
Library updates
The following libraries have been updated to improve compatibility and functionality:
- Updated the JDBC driver URL for Athena DB to use the new format compatible with Athena JDBC driver version 3.x.
- Upgraded the FTA library to the latest version to enable detection of additional semantic types, including India-specific types, and to improve locale support.
Corrected issues
| Issue Summary | Issue Number |
|---|---|
| Fixed a date conversion issue in the External Start Event node that occurred after upgrading from version 10.2 to 12.2. This issue prevented process models from running when a system date was used as the reference start time or reference end time. | ISX-23734 |
| Fixed an issue that caused SAML logins to fail due to a Content Security Policy (CSP) violation when POST binding was used for the authentication request. | ISX-23731 |
Fixed an issue where the latestfilter did not work when used with a Rangetype date filter in dashboards. |
ISX-23716 |
| Fixed an issue where non-admin users encountered an error when exporting stages that contained comments authored by other users. | ISX-23714 |
| Corrected the column headings in the data table emailed from the Notify With Data Table task in process models so that they match the order shown in the Data Table tab. | ISX-23702 |
| Fixed an issue where the dashboard ran an unnecessary distinct value query whenever a text field or range filter was applied, which could lead to performance degradation with large datasets. | ISX-23636 |
| Fixed an issue where the Data360 Govern integration failed to update existing DQ+ technical assets during full or incremental synchronization after changes were made to those assets. | ISX-23602 |
Fixed an issue that prevented the
DEPLOY_CSP_REPORT_ONLY deployment property from
working correctly when it was set to true. |
ISX-23732 |