Lineage is widely available in modern data platforms — but it is often incomplete. Most tools can trace a table or render a DAG. At enterprise scale, that is not enough. Data flows across schemas, pipelines, and BI layers before it reaches a decision-maker. Teams need to see that full journey, not just individual asset relationships.
When something changes upstream, the questions that matter are: How does this change propagate across schemas, pipelines, and reporting layers? Which business dashboards and reports depend on it? How far does the impact extend? Traditional lineage answers these questions partially at best — showing relationships at a single level without connecting them into a coherent end-to-end view.
Acceldata 26.4.0 delivers capabilities across three areas that move lineage from isolated asset-level views to a connected picture of how data flows and how changes propagate across the enterprise:
- Aggregated lineage at the schema and asset collection level
- End-to-end lineage across the Power BI business layer
- Improved lineage across SnapLogic and Snowflake pipelines
From Asset-Level Lineage to Workflow-Level Visibility
Asset-level lineage is a useful starting point, but it often stops too early. Seeing the upstream and downstream relationships for a single table does not capture how data flows across a broader workflow. In enterprise environments, data moves across schemas, domains, and systems before it reaches any business output. When lineage is viewed one asset at a time, teams must reconstruct that broader workflow manually.
This release extends lineage beyond individual assets by introducing aggregated views at the schema level and across user-defined collections of assets.
Schema-Level Lineage
Rather than tracing one table at a time, lineage can now be viewed across all assets within a schema — providing a consolidated view of upstream dependencies and downstream consumers for an entire domain. For teams that organize data by function, such as reporting, billing, or analytics, this makes it straightforward to understand how data flows into and out of that domain as a whole.
Asset Collection Lineage Across Schemas
Lineage can also be viewed for collections of assets spanning multiple schemas, defined using filters, tags, or labels. This allows teams to analyze lineage around a business workflow rather than a technical boundary. Assets involved in a regulatory reporting pipeline, for example, can be grouped and analyzed together even if they reside across different schemas.
Deeper Traceability and Exploration
Aggregated lineage includes upstream and downstream relationships and supports function-level lineage nodes for deeper traceability. Users can search by asset or node name and explore lineage interactively through both table and graph views.
Example use case: A banking team managing regulatory reporting needs to understand how data flows from trading systems through risk calculations into reporting schemas. With schema-level and collection lineage, they can view the full workflow at once rather than tracing individual tables — enabling faster impact analysis, improving audit readiness, and reducing the risk of incorrect reporting.
Extending Lineage to the Business Layer (Power BI)
Lineage that stops at data assets misses the layer where data actually drives decisions. This release delivers end-to-end lineage across the full Power BI hierarchy — from source tables through dataflows, semantic models, and reports, all the way to dashboards and individual tiles.
Column-level traceability, real-time impact propagation, and data quality context are carried through into BI assets. When an upstream source changes, the affected reports and dashboards are immediately identifiable — without manual investigation across tools.
More detail: See the dedicated Power BI lineage blog for full capability coverage.
Tightening Lineage Across Pipelines (SnapLogic–Snowflake)
In real-world environments, lineage frequently breaks at integration layer boundaries. This release closes those gaps by extracting lineage for Snowflake assets used within SnapLogic pipelines and surfacing relationships across nested and inter-pipeline dependencies.
Teams can now trace issues across pipeline boundaries — from orchestration through transformation — without manually reconstructing the connections between systems.
More detail: See the dedicated SnapLogic–Snowflake lineage blog for full capability coverage.
Across these three areas, lineage in Acceldata 26.4.0 spans schemas, pipelines, and the business layer — providing a connected, operational view of how data moves through the enterprise and how changes propagate from source to output.
Available Now
All lineage capabilities described here are available as part of the Acceldata 26.4.0 release. Reach out to your Acceldata Customer Success contact or visit the documentation portal for setup and configuration details.
.webp)
.webp)
