Release7.2.4.7
This release introduces key fixes across Chrome Extension, Data Quality, Query Sheet, and Impact Analysis, improving usability, visual accuracy, access control, query execution reliability, and lineage impact reporting.
Key Highlights
Chrome Extension: Fixed repeated pop-up interruptions in Power BI by restricting pop-up activation to manual user actions only.
Data Quality:
Corrected the Passed status color in Data Quality rule summaries to consistently display in green after rule execution.
Updated rule name validation to support the period (.) character, ensuring consistent handling of special characters in Data Quality rule names.
Fixed access validation logic so roles with valid data read permissions can view failed values in Data Quality rules.
Query Sheet: Improved SQL formatting handling to prevent syntax errors when queries are pasted without line breaks, ensuring reliable query execution.
Impact Analysis: Corrected impacted object count calculations to display 0 when all lineage has been removed, ensuring accurate impact reporting.
Release Details:
Hotfix Release
Release7.2.4.7
Release7.2.4.7.7247c16f3e7
27th Jan 2026
Chrome Extension
Fixed
Chrome Extension Pop-Up Trigger Fix
In the Chrome Extension, an issue was identified where the extension pop-up appeared repeatedly while working in the Power BI application. The pop-up was triggered on every browser activity, such as clicks or page refreshes, causing frequent interruptions.
This behavior has been addressed by changing the pop-up activation to occur only through a manual action, preventing automatic pop-ups during routine browser interactions.
Data Quality
Fixed
Corrected Passed Status Color in Data Quality Rules
In Data Quality, an issue was identified in which the Passed status appeared in red instead of green in the data quality rule summary. The status color was incorrectly displayed after running custom data quality rules.
This issue has been resolved by correcting the status color logic, ensuring that Passed now consistently appears in green.
Special Character Handling in DQ Rule Names
In Data Quality, an issue occurred in which special characters such as >, <, and != were no longer accepted in data quality rule names, even though they had previously been allowed. This restriction caused existing rule names with special characters to be rejected.
The validation logic was updated to support the period (.) character in data quality rule names while maintaining consistent naming rules.
Resolved Access Issue for Failed Values in Data Quality Rules
In Data Quality, an issue where a business role with read access could not view failed data values in Data Quality rules has been resolved. The system incorrectly restricted visibility of failed values for non-admin roles, even when data read permissions were present.
Access validation logic was updated to ensure that roles with valid data read permissions can view failed values in Data Quality rules.
Query Sheet
Fixed
Improved SQL Formatting Handling in Query Sheet
In the Query Sheet, an issue where SQL queries were not properly formatted during execution caused valid queries to fail with syntax errors. When queries were pasted without line breaks, the system incorrectly combined keywords, leading to parse errors and failed jobs.
This issue has been resolved by improving query formatting handling, ensuring queries execute correctly even when pasted without manual spacing adjustments.
Impact Analysis
Fixed
Corrected Impacted Object Count When Lineage Is Removed
In Impact Analysis, an issue where the impacted object count did not display 0 after all lineage was removed has been fixed. The impacted object count was not updating correctly when no impacted objects were present.
This issue has been resolved by updating the calculation and display logic to show 0 when no impacted objects exist.
Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.
Last updated
Was this helpful?