Explore data lineage

Screenshot note: Screenshots are illustrative. Controls or labels may remain untranslated in the demo release, and pages without a faithful English capture retain the source illustration. Control names and layouts can vary by release.

Data Catalog starts from harvested metadata for precise table, field, report, or metric lookup. Lineage Map starts from parsed objects for an overall view of flows.

Choose an exploration path

Aspect	Data Catalog	Lineage Map
Content	Harvested metadata	Saved parsing results
Purpose	Find a known object	Explore cross-level flows
Filters	Keywords, system, source, type, tags	Global and in-graph search, level, depth, tags
Detail	Business names, field types, and metadata	Simplified objects emphasizing relationships
Next actions	View lineage, add to a scenario	Drill down, filter, analyze impact, export

Use Data Catalog

1. Open Data Catalog and search a name or keyword.
2. Filter by application system, source, and asset type.
3. Add tags or owner criteria as needed.
4. Verify object type, path, and system.
5. Open lineage or add the object to a scenario.

Investigate mismatches

Condition	Display	Action
Table metadata without table lineage	Metadata and fields remain visible; paths can be absent	Check file harvesting and parsing
Table lineage without metadata	Difference styling; field types may use default icons	Check harvesting scope and namespace
Field metadata without lineage	Field appears in the metadata drawer without a relationship	Check granularity and SQL
Field lineage without metadata	Difference styling	Check field harvesting, names, and mappings

These differences usually indicate that harvesting, parsing, and object identity are not aligned.

Use Lineage Map

1. Open Lineage Map and globally search one or more schemas, entities, or properties.
2. Choose upstream, downstream, or full lineage.
3. Drill from schema to entity or property level.
4. Adjust depth to control expansion.
5. Use in-graph search to locate displayed objects.
6. Filter by tags or entity types.

Map object counts can differ from catalog counts. Verify current object, namespace, and system. Use a scenario for persistent monitoring of a defined scope; ask an administrator to investigate space, namespace, and parsing details for mismatches or breaks.

The current English environment did not provide a stable, distinct catalog-search capture. Follow the filters and object checks above, then confirm the deployed catalog layout.

Verify results

Check environment identity, metadata attributes against harvested results, and graph direction against actual processing. Record mismatches and assign harvesting or parsing owners.

Related guides

• View lineage
• Application scenarios
• Administration