> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/hotfix-releases/release7.2.5.x/release7.2.5.28.md). # Release7.2.5.28 This release introduces key enhancements and bug fixes across Tags, Data Catalog, Data Products, Service Desk, Lineage, Connectors, Advanced Jobs, and Schedule, improving tag management, access control, lineage accuracy, notification consistency, metadata completeness, usage reporting, and job availability. **Key Highlights** * **Tags**: Fixed bulk upload validation for child tags under existing master tags, allowing successful uploads without invalid tag errors. * **Data Catalog**: Corrected permissions checks for Power BI report pages, ensuring restricted pages no longer appear in the Sub Reports tab after access is removed. * **Data Products**: Resolved missing upstream and downstream relationships in the Data Product Lineage tab, ensuring available connections are displayed consistently. * **Service Desk**: Fixed unexpected warning messages in Teams notifications for content change requests, ensuring notifications display only the configured template content. * **Lineage**: * **Denodo**: Resolved incomplete lineage generation for tables and views, including missing column-level lineage. * **SharePoint Online**: Corrected the lineage icon display to show the appropriate SharePoint Online icon for assets. * **SSRS Reports**: Fixed query parsing and dataset mapping issues, ensuring successful processing of queries containing the CONTEXT keyword and consistent dataset information across sections. * **Connectors**: * **Power BI Paginated Reports**: Fixed missing source code after crawling, ensuring report source information is available in the data catalog. * **Power BI**: Corrected custom field population for TCF7 (Connector Type), TCF8 (Connection String), and TCF9 (Username), ensuring values are populated for both new and existing assets. * **Advanced Jobs**: Fixed the MicroStrategy Usage Stats job to ensure user usage statistics process and display as expected. * **Schedule**: Resolved a migration issue that caused scheduled jobs to disappear from the Job Workflow page, ensuring migrated jobs remain available and run as expected. **Release Details:**
Release TypeRelease VersionBuild<Release. Build Number. Release Stamp>Build Date
Patch ReleaseRelease7.2.5.28release7.2.5.28.72528.37131ecSeptember 08, 2026
## Tags ### Fixed **Resolved Bulk Upload Validation for Child Tags** In Tags, an issue where bulk tag uploads through LMDF failed with the error “Please enter a valid tag” when adding child tags under an existing master tag has been resolved. The master tag was already created, but the upload did not recognize it. The validation has been corrected to allow bulk uploads under existing master tags. ## Data Catalog ### Fixed **Resolved Visibility of Restricted Report Pages** In Data Catalog | Reports, an issue where restricted Power BI report pages remained visible in the Sub Reports tab even after access was removed has been resolved. The permissions check has been corrected to ensure pages without access no longer appear in the Sub Reports tab. ## Data Products ### Fixed **Resolved Missing Relationships in Data Product Lineage** In Data Products, an issue where the Lineage tab displayed only the Data Product node instead of its available upstream and downstream relationships has been resolved. The lineage graph did not consistently display connected data objects, even though the required information was available. The lineage display has been fixed to ensure the Data Product Lineage tab consistently shows available upstream and downstream relationships. ## Service Desk ### Fixed **Service Desk Teams Notification Template Fix** In Service Desk, an issue where Teams notifications included an unexpected warning message that was not part of the configured notification template has been resolved. The warning appeared in notifications for content change requests, even though it was not included in the template’s subject or body. The notification process has been corrected to prevent the warning from appearing in the configured template. ## Lineage ### Fixed **Denodo Lineage Generation Fix** In Denodo, an issue where lineage was built for some tables and views but not others, and column-level lineage was missing, has been resolved. The lineage process has been fixed to ensure applicable tables and views generate lineage correctly, including column-level lineage, without errors. **SharePoint Online Icon Display Fix** In the SharePoint | Lineage tab, an issue where SharePoint Online assets displayed a generic icon instead of the SharePoint Online icon has been resolved. The lineage graph showed the assets, but the missing icon made it difficult to identify their source. The icon display has been corrected to show the SharePoint Online icon for these assets. **SSRS Reports | Query Parsing and Dataset Mapping Fix** In SSRS Reports, an issue where queries containing the unsupported CONTEXT keyword failed during parsing, preventing lineage generation, has been resolved. The dataset information displayed in the Correct Query section also did not match the Query and Lineage section. For example, the Correct Query section displayed four datasets, while the Query and Lineage section displayed only three. The query parsing and dataset mapping issues have been fixed to ensure successful query processing and consistent dataset information across both sections. ## Connectors ### Fixed **Resolved Missing Source Code in Paginated Reports** In Power BI | Paginated Reports, an issue where reports were available in Power BI and successfully crawled into the Data Catalog, but their source code was missing, has been resolved. The crawl process attempted to retrieve the report source but did not populate it in the data catalog. The source retrieval process has been corrected to ensure that the source code is available after crawling. **Power BI Custom Field Population Fix** In Power BI, an issue where custom fields (TCF7 (Connector Type), TCF8 (Connection String), and TCF9 (Username)) were not populated consistently during crawling has been resolved. The crawler now automatically populates these fields for both newly crawled and existing assets. The values are reflected in the catalog after the crawl completes. ## Advanced Jobs ### Fixed **Resolved Missing MicroStrategy Usage Statistics**\ In Advanced Jobs, an issue where the 'MicroStrategy Usage Stats' job completed successfully but did not populate or display MicroStrategy user usage statistics has been resolved. The job logs showed that processing started successfully, but the application did not reflect any usage data. The job has been fixed to ensure that MicroStrategy user usage statistics are processed and displayed as expected. ## Schedule ### Fixed **Scheduler Jobs Migration Issue Resolved** In Scheduler Jobs, an issue where scheduled jobs disappeared from the Job Workflow page after migrating from version 6.3.4.80 to 7.2.5.12 has been resolved. The fix ensures scheduled jobs appear on the Job Workflow page and run as expected. *** Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.ovaledge.com/hotfix-releases/release7.2.5.x/release7.2.5.28.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.