Skip to main content

Release notes 26.2.4

· 4 min read

Dataedo 26.2.4 delivers several Data Lineage improvements, including outer apply parsing support, enhanced column lineage behavior, and flow visualization fixes. This release also introduces a series of Export to Excel enhancements, Description text editor additions, and refinements to Data Profiling and Data Classification, along with a number of bug fixes across Portal and Desktop.

Portal:

  • Portal can now be deployed as a child app under an existing IIS site instead of creating a new root site.
  • Flow details icons are now always visible when inspecting Lineage Flow.
  • The process icon in Lineage diagrams now properly redirects to the process tab.
  • Outer apply is now supported during Lineage parsing.
  • Homogenized the behavior of column lines when adding inflows — if too many columns are expanded, column lineage will not be available for any of them.
  • Ensured proper parsing of SQL_Query during Data Lineage building.
  • Adjusted Data Profiling matching protocol — column name match is now treated with the same weight as other match types.
  • Fixed redirects from Data Classification to Steward Hub's columns requiring review module — redirects still lead to the currently open database, unless it does not exist in Steward Hub. Then you will be taken to the first database that requires your attention.
  • In Data Classification, Semantic Type rules with a regex pattern valid in non-JavaScript engines (e.g. (?i)) no longer fail validation.
  • If an import summary failed after connection to a data source was already finalized (e.g., when saving the extracted metadata to the repository or when creating linked sources), the import status will be shown as failed, with a correct error message.
  • Export to Excel
    • ensured that Date, Boolean, and decimal/float values are emitted as their respective cell types, rather than plain text.
    • resolved an issue that could sometimes prevent viewing details of past configurations.
    • fixed a visual bug that caused configuration details to shift downwards when opened.
    • ensured that all values are properly displayed in the resulting .xlsx file.
    • unused sections are hidden in the summary sheet of the resulting .xlsx file.
    • clicking an export-ready notification while already on the /export page now correctly triggers the file download every time.
    • if the row number exceeds the maximum number of rows in an Excel sheet, a given category will be spread over multiple sheets (e.g., Columns, Columns(1), Columns(2), etc.).
  • Added a copy button to code blocks, enabling viewers, explorers, and data community members to safely copy code snippets.
  • Description text editor:
    • code blocks with a specified code language can now be added by typing ```{LANGUAGE} (LANGUAGE should be the name of a programming language you want your code block to represent).
    • you can now escape default rendering with ctrl+.
    • fixed an issue that required double-clicking Enter to move to the next line when writing a code snippet.
    • adjusted the behavior of Save/Cancel buttons; buttons are no longer displayed if no changes were made.
  • Images can now once again be added to the Info Box in Portal's Customization settings.
  • Custom Fields of the Closed List type can be deleted again.
  • Fixed a bug that caused some grids to crash when loading data of objects with badges.
  • Fixed an issue where opening assets could cause an HTTP 500 error.
  • The Wrong connector selected pop-up can now be closed.

Connectors:

  • Bugfixes:
    • Azure Data Factory — added a helper that truncates auto-generated names exceeding the character limit.
    • Snowflake — adjusted Lineage queries to properly handle special characters, added support for external functions, added better feedback regarding failed executions.
    • Power BI — fix for a workspace scanning error (RoleTablePermission) during import

Desktop:

  • Resolved an issue that caused import crashes during bulk operations.

Misc:

  • Support for signed SAML AuthnRequests added, it can be configured using appsettings.json or docker environment variables.