Release6.3.1

OvalEdge Release6.3.1 introduces enhanced AI recommendations for data classification and lineage visibility in DBT and Azure Synapse connectors. The release includes new system settings and advanced jobs for greater control over application diagnostics. 

Bug fixes across various modules and connectors have been addressed to ensure a smoother experience.

Minor Enhancements

Data Classification

• The AI Recommendations are improved by introducing AI recommendation keywords. Users can set up AI recommendation keywords for the term. These keywords will be used during the AI recommendation, and the data objects that match the keywords will be recommended, increasing the smart score. 
  For example, if the term is "DOB," the synonyms can be "Date Of Birth," "birthdate," etc.

• Current Terms View: The Data Classification Recommendation AI Model Summary now has a new column, "Current Terms." Users can view the current term along with the recommended term associated with the data object.
• Download Recommended Data Objects: Users can now download the details of recommended data objects directly to their desktops from the Term Summary, Recommendation tab. 

Connectors

• The DBT Connector now provides detailed lineage information, including both column-level and table-level lineage.
  • Column-Level Lineage: Users can see how each data column is transformed within DBT pipelines.
  • Table-Level Lineage: Users can view the overall movement of data between tables.
    This enhancement offers a more comprehensive understanding of data transformations and flows.

• The Azure Synapse Connector has been improved. Users are now required to execute an “Intelligent ADL Catalog” advanced job before building lineage. This step ensures that all ADL Files are cataloged, resulting in complete data cataloging and enhanced visibility.

New System Settings

The latest release introduces new settings that enhance user control over the application's behavior. 

New Advanced Jobs

The latest release introduces a set of new advanced jobs that allow users to update the data specific to modules or features using advanced algorithms.

Bug Fixes

In Release6.3.1, the following bugs have been resolved, ensuring the OvalEdge application functions as expected.

Tags

• In the Tags Summary, an issue where users couldn't view the status of tags in the application but could view it when they downloaded the list has been fixed. Users can now view the tag status in the application as expected.

Data Catalog

• In the Tables Summary, the issue with profiling on a table with no data incorrectly showing the status "Profile Failed" has been resolved. The status is now accurately displayed as "No Data Available for Profiling" for tables without data.
• In the Reports Summary, an issue where Viewer users could not navigate to the service request page from the "Report Data Access Request" option in the 9-Dots menu, even when the report was certified, has been resolved. Viewer users can now access the service request page as intended.
• In the Code Summary, an issue where the object name in the breadcrumb path was mismatched has been resolved. Users can now view the correct object name in the breadcrumb path.
• In the Data Catalog > File > Folder Summary, an issue where clicking on the Folder OvalSight displayed an unclear error message "Technical Issue" if the folder wasn't set up correctly has been resolved. Now, users can view the message "Configure folder analysis custom temp path" if there's an issue with the folder path.
  Resolution Steps: Navigate to Administration > System Settings > Others, search for the key folder.analysis.user.custom.path, and add the default path.

• In the Data Catalog and Business Glossary, an issue with bullet justification in the Business, Technical, and Detailed descriptions has been resolved. Users can now edit or enter the description text using bullet points and numbered lists.

Business Glossary 

• In the Term Summary, the issues with mismatched associated object counts and pagination counts have been resolved. Users can now view the correct number of associated objects with accurate pagination.
• In the Business Glossary List View and Tree View, an issue where sorting data in the Domain, Category, Subcategory, Terms, and other columns was not working has been resolved. Users can now sort data in ascending or descending order by specific columns.

Data Quality Rules

• In the Data Quality Rules Date Validation function, an issue where the input date would disappear when the operator was set to "Equal To" and the Success Criteria was set to "Result Value as Percentage" has been fixed. The Date Validation function now retains the selected date and works as expected.
• In the Data Quality Rules, an issue where the Failed Data Query Results displayed correctly in the Code Summary Results page but were disordered in the email sent to contacts has been resolved. Now, results are shown in the proper order, such as First Name and Last Name, in both the Code Summary Results page and the email.
• In the Data Quality Rules, an issue where the Valid SSN Format function, when selected with the Percentage operator for a table column, showed incorrect results for passed and failed counts has been resolved. The rule is now executed successfully, providing accurate results.m
• In the Data Quality Rules, there was an issue where associating a data object(s) didn't show up while creating a new rule, but after saving the rule, the added object(s) appeared in the summary. This issue has been resolved, and the data object(s) are visible while creating a new rule.
• In the Data Quality Rules, an issue where an error message appeared for a Data Quality Rule with associated SQL objects when using a filter has been resolved. The most common cause of this error is when the user needs the SHOWPLAN permission for the database they are querying. To fix this, an administrator can grant permission using the following SQL command: GRANT SHOWPLAN TO UserName.
• In Data Quality Rules, the issue where the "Last Run On" and "Last Modified On" timestamps display the exact date and time after executing a rule has been resolved. Users can now view accurate "Last Run On" and "Last Modified On" timestamps.
• In Data Quality Rules, an issue where the filter beside the schema in the pop-up for adding associated objects was not working properly has been resolved. Users can now filter schemas and add the required objects accurately.
• In Data Quality Rules, an issue where the pop-up for adding additional associations to associated objects only displayed connectors linked with the object, omitting the remaining connectors, has been resolved. Users can now view and add all required objects.
• In Data Quality Rules Summary > Object Execution Results, an issue where users previously encountered an error when attempting to download the list of failed values has been resolved. Users can now view and download the list of failed values as expected.
• In the Data Quality Rules Summary, Associated Objects, an issue with the quick view icon taking longer to open and display associated tables or columns in the background has been resolved. The quick view icon now opens promptly and shows at the top of the page.
• In the Data Quality Rules Summary, an issue where the "Should Have Unique Values" function previously returned only results without displaying stats or failed values has been resolved. Users can now view detailed stats and failed values as intended.
• In Data Quality Rules, an issue preventing users from viewing failed values by clicking the quick view icon in the Object Execution Results has been resolved. Users can now view the failed values in the popup as expected.
• For the Azure Synapse Connector
  • An issue caused by the Empty or Null Data Values function throwing an error when executing the rule for all data objects has been resolved. The rule is now executed successfully, providing accurate results.
  • The Filter function using a "Where Clause" in Advanced Settings caused an error when running the rule on specific data has been resolved. The rule is now executed successfully, providing accurate results.
  • For the connection established through Bridge and Azure Key Vault, an issue caused by the following functions throwing an error when executing the rule for all data objects has been resolved. 
    • Data Length
    • Date Validation
    • Number Validation
    • Non-Empty and Non-Null 
    • Word Count 
    • Valid Email
    • Maximum 
    • Minimum
    • Distinct
    • SSN Format
    • Credit Card Format
    • Empty or Null Values 

These functions are now executed successfully, providing accurate results.

Jobs

• In the Jobs, an issue where crawling failed in the ADF (Azure Data Factory) schema, displaying a generic error message "either no tables present or access denied." has been resolved. Users now see a relevant error message related to the ETL connection for ADF crawling failures.

Advanced Tools

• In the Load Metadata from Files, an issue where Governance Roles did not appear in the application after uploading Report Columns, despite a successful Load Metadata from Files job, has been resolved. Users can now view the Governance Roles uploaded through Load Metadata from Files.
• In the OvalEdge API, when using the API "/API/connector/saveconnector" to create a connector, previously, if governance roles that didn't exist in OvalEdge were provided, the connector would still be created instead of generating an error. This issue has now been resolved, and the connector will only be created if the governance roles provided exist in the OvalEdge User and Roles.

Administration 

• In the Security > Domain Classifications, an issue where existing domains with default unchecked classifications were incorrectly displayed, as checked on the related Term summary page, has been resolved, and the Classifications now display correctly according to their settings.
• In the Users & Roles > Roles, an issue where the Add New Role icon was disabled after updating the license type (other than default) has been resolved. Users can now add a new role after updating the license type.
• In Connector Security, an issue where the error message "Technical Issue. Retry later" was displayed when attempting to update Governance Roles for all connectors in bulk has been fixed. Users can now update Governance Roles in bulk without encountering any issues.
• In the Service Desk Templates, an issue with selecting manual fulfillment for custom templates behaving like automatic fulfillment has been resolved. Users can now choose manual fulfillment and update the remaining fields manually as expected.
• In the Advanced Jobs, an issue where users encountered errors when running the "Migrate favorite dashboard to new dashboards flow" advanced job has been resolved. Users can now migrate their favorite dashboards to new dashboards without encountering errors.
• In the Advanced Jobs, an issue where running the "Custom Fields Migration" advanced job multiple times caused duplicate custom fields and data loss in the value field has been resolved. Now, the job allows users to run only once during migration to avoid duplications and data loss.
• In the Advanced Jobs, an issue where users previously experienced formatting issues when uploading a data story via "Data Stories Migration" has been resolved. Users can now view the data story in the correct format.
• In the Custom Fields, an issue where the confirmation window displayed the wrong message when deleting a Date Custom Field has been fixed. The updated confirmation message now displays, "Deleting <Custom Field Name> (DOB) will remove the values from objects. To prevent accidental deletion, confirm by entering the field names below." Users must enter the field names to proceed with the deletion.
• In the System Settings > Notifications > Notification Templates, users were experiencing an issue where, when searching for a keyword in the Data Quality Rule's notification message, the same previous search keyword would display when searching in another notification template. This issue has been fixed, and users can now search in notification templates without the previous search keyword being displayed.

Connectors

• For the Snowflake Connector, an issue where users encountered an error when executing queries in the Query Sheet has been resolved. Queries with the "WITH" condition are now supported, allowing users to execute queries without errors.
• For the FME Connector, an issue where users encountered a null pointer error while attempting to build lineage due to missing files has been resolved. Support for handling missing files has been implemented, allowing users to build lineage as expected without errors.
• For the SAAS On-Prem Connector, an issue preventing users from building column-level lineage for certain columns has been fixed. Additional support for symbols, such as converting French-language special characters to US English, has been implemented so that users can now correctly build column-level lineage for all the columns.
• For the Power BI On-Prem Connector
  • An issue where users encountered a null pointer exception when running the "PowerBI columns curated info moving from report to dataset" advanced job after migrating the database to the latest version has been resolved.  Users can run the advanced job without exceptions and retrieve PowerBI columns curated info from the report to the dataset.
  • An issue causing duplicate columns to appear in the column-level lineage from semantic tables to reports has been resolved. Users can now build lineage accurately without encountering duplicate columns.
• For the Amazon DMS Connector, an issue where users encountered a null pointer error when trying to build lineage has been resolved. The Schema lineage has been restricted, allowing users to build lineage for tables and table columns without errors.
• For the Spline Connector, an issue preventing users from viewing crawler settings while editing the connector has been fixed. Users can now view the crawler options in the menu.
• For the Qlik Cloud Connector, the issue causing a data truncation error when crawling reports due to the child name column length being 512 has been resolved. The column length has been increased to 750, allowing users to crawl reports successfully.
• For the ADL Connector, an issue where parquet files' data was not displayed in the Data Catalog > Files > Data tab after crawling and cataloging has been resolved. Users can now view parquet file data in the Data tab.
• For the Power BI Cloud Connector, when crawling is performed on the reports and dataflows, only certified endorsements are displayed in the  Data Catalog > Reports > Endorsement column. The feature has been improved, displaying certified and prompted report endorsements.
• For SAP Connectors, users previously encountered an issue where the search text bar for selecting tables did not clear previous entries and threw an error. This issue has been resolved, and users can now search and choose tables accurately.
• For the Manual Connectors, an issue where users could not edit the connector has been resolved, and users can now successfully edit the Manual Connectors.
• In the Connectors, an issue where there is no provision for connecting to SAP S/4 HANA through SAP Tables has been fixed. Users can now connect to different SAP Systems, including SAP S/4 HANA, SAP ERP, SAP CRM, SAP SRM, SAP SCM, SAP PLM, SAP Industry Solutions, SAP HCM (Human Capital Management), SAP BW, and others.
• In Connectors, there was an issue where, after building lineage for report connectors, the user was unable to navigate to the specific report's source page. This issue has been fixed now. Users can navigate to the selected report's source page from the 9-Dots Menu action for the selected report.

Copyright © 2024, OvalEdge LLC, Peachtree Corners, GA USA