> 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/release8.2/minor-release/release8.2/release-notes/lineage.md). # Lineage ## New & Improved ### Auto Lineage | Connector Name Display in Jobs In the Lineage module, BUILD\_LINEAGE jobs did not display the associated connector name in the Jobs interface, making it difficult to identify the connector associated with lineage processing. The functionality has been updated, and now the connector name is displayed for lineage build jobs in the Jobs page. 👉 For more details, see [Build Auto Lineage section](https://docs.ovaledge.com/release8.2/advanced-tools/build-auto-lineage/build-auto-lineage) ### Association | Support for Procedures, Functions, Views, and Triggers In the Lineage module, the Association feature did not support Procedures, Functions, Views, and Triggers during manual lineage creation, resulting in incomplete object relationship mapping. The functionality has been updated and now the Association feature supports Procedures, Functions, Views, and Triggers to provide broader relationship mapping and lineage visibility. The following improvements have been implemented: * Added Association support for Procedures, Functions, Views, and Triggers * Expanded object relationship mapping across supported object types * Added support for impact analysis across associated objects ### Azure Data Factory Connector | AI-Augmented Lineage In the Azure Data Factory Connector, lineage generation required improved interpretation of pipelines, activities, and transformation logic to support automated dependency mapping. The functionality has been updated and now AI-augmented lineage generation is supported for Azure Data Factory pipelines. The following improvements have been implemented: * Interpret Azure Data Factory pipeline JSON definitions for lineage generation * Support activities such as Copy, Data Flow, and Lookup for lineage mapping * Handle parameterized and dynamic pipeline structures * Generate dependency relationships across pipeline components * Standardize lineage extraction logic for ADF artifacts 👉 For more details, see [Supported Connectors section](https://docs.ovaledge.com/release8.2/advanced-tools/build-auto-lineage/ways-of-building-auto-lineage?fallback=true#supported-connectors) ### Lineage Status | Standardized Status Mapping In the Lineage module, the status values were inconsistent across different execution scenarios, leading to variations in status representation. The functionality has been updated and now standardized lineage status values are applied across all supported scenarios. The following improvements have been implemented: * Update “Lineage Build Successfully” to “Lineage Built Successfully” * Update “Lineage Built with Associations” to “Lineage Built only with Associations” * Update “Success Lineage Fixed” to “Lineage Built with OvalEdge Lab” 👉 For more details, see the [Viewing Source Codes section](https://docs.ovaledge.com/release8.2/advanced-tools/build-auto-lineage/ways-of-building-auto-lineage?fallback=true#viewing-source-codes) ### Lineage Parsing | Error Bucket Categorization In the Lineage module, lineage parsing errors were displayed as raw technical messages, making it difficult to interpret failure reasons. The functionality has been updated, and now errors are grouped into categorized error buckets with support for a detailed error view. The following improvements have been implemented: * Replace technical error messages with categorized error buckets * Display structured error information for lineage parsing failures * Provide a detailed error view for troubleshooting purposes 👉 For more details, see the [Viewing Source Codes section](https://docs.ovaledge.com/release8.2/advanced-tools/build-auto-lineage/ways-of-building-auto-lineage?fallback=true#viewing-source-codes) ### ADF Lineage | AI Enhancement In the Azure Data Factory Connector, lineage extraction from pipeline definitions lacked completeness and consistency. The enhancement has been implemented, and now AI-based lineage generation supports full ADF pipeline interpretation. The following improvements have been implemented: * Enabled AI interpretation of ADF pipeline JSON * Improved handling of transformations and parameters * Automated lineage relationship generation * Enhanced scalability for large pipeline structures 👉 For more details, see the [Supported Connectors section](https://docs.ovaledge.com/release8.2/advanced-tools/build-auto-lineage/ways-of-building-auto-lineage?fallback=true#supported-connectors) ### Build Lineage | Tracking Columns In the Build Lineage screen, Start Date and Job Id were not available for tracking lineage execution. The enhancement has been implemented, and now both fields are visible for improved traceability. The following improvements have been implemented: * Added Start Date column for lineage execution tracking * Added Job Id column for job identification * Improved visibility of lineage build timelines * Enhanced traceability of execution workflows 👉 For more details, see the [viewing Source Codes section](https://docs.ovaledge.com/release8.2/advanced-tools/build-auto-lineage/ways-of-building-auto-lineage?fallback=true#viewing-source-codes) ## Fixed ### Python Lineage | AI Parsing In the Lineage AI module, Python-based lineage parsing was inconsistent in generating structured lineage outputs. The issue has been resolved, and now AI parsing produces structured Python lineage JSON accurately. The following improvements have been implemented: * Enabled AI-based parsing of Python scripts for lineage extraction * Generated structured lineage JSON with tables and relationships * Extracted embedded SQL and transformation logic correctly * Improved validation of lineage results 👉 For more details, see the [Handling Complex Transformations section](https://docs.ovaledge.com/release8.2/advanced-tools/build-auto-lineage/ways-of-building-auto-lineage?fallback=true#handling-complex-transformations) *** 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/release8.2/minor-release/release8.2/release-notes/lineage.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.