Skip to main content

Release notes 26.2.2

· 2 min read

Dataedo 26.2.2 delivers a series of Excel Export improvements, an ER Diagram UI overhaul, and several Portal fixes addressing URL crashes, Metadata Import behavior for deleted procedures and functions, and drag-and-drop issues in Manual Object's creation wizard. This release also refines Metadata Sync's conflict resolution wording, enhances Import Summary, and resolves a Power BI null handling issue to prevent Import failures.

Portal:

  • Fixed an issue where trailing backslashes in the URL caused some pages to crash
  • Deleted procedures and functions are no longer re-imported during the next scheduled Metadata Import
  • Fixed an issue that caused the Data Sources page to be inaccessible during Metadata Import for some users
  • Resolved issues that caused a crash when using drag-and-drop to sort columns in Manual Object's creation wizard
  • Changed wording relating to conflict resolution in Metadata Sync's settings: Take Dataedo -> Prioritize Dataedo; Take Source -> Prioritize Source
  • Improved the Excel export functionality — slight UI changes, better handling of duplicate object names, improved navigation between the export page and execution calendar, added a Canceled status to mark manually terminated exports
  • Fixed the behavior of Report Usage counters in Import Summary
  • Unused tabs are now hidden in Import Summary — so for example, the Data Lineage tab will not be displayed for sources where Lineage Extraction is not configured
  • Bugfixes in Data Lineage Diagrams — +inflow/outflow buttons now always properly expand the diagram, added proper handling of type 500 exceptions
  • Improved UI for ER Diagrams — diagrams are now displayed in fullscreen mode, and the settings icon is now accessible from every ER Diagram configuration
  • Resolved an issue, where column and relation-level filters wouldn't properly apply in ER Diagram views

Connectors:

  • Power BI — improved null handling logic to prevent Import failures

API

  • Resolved an issue where empty Custom Fields could cause indexing mismatches in GET requests