Alation: Two dashboards say ‘orders’. Which lineage should you follow?

Trace a fictional metric to its definition, owner and effective version before choosing a catalog.

Source: www.alation.com
August 25, 2026
2 min

Alation’s March 2025 glossary describes lineage as the path from source through transformation to reporting. A catalog helps when a measure crosses warehouses, models and dashboards. If the disagreement lives in one table with one owner, start with a versioned definition document. A catalog does not mean every edge is captured or decide which business definition should win.

Reconcile two event types

Make up one day: 100 orders were created and eight of those canceled; the fulfillment event table records 72 fulfillments that day. Net new orders are 92, fulfillments 72. Both dashboards can be valid despite the same ‘orders’ label. Record their event time field, status filter and definition version separately. Ask another reviewer to trace each dashboard through its model to the source on paper, not on a live system.

Article img
Fictional day: 100 created minus 8 canceled leaves 92 net; a separate 72 fulfillment events.

Original comparison, not Alation UI. Net new orders and fulfillments use different events despite a shared label.

Test one handoff

Pass only if a reviewer can find the relevant definition, effective date and responsible owner in one handoff and explain why the other value differs. Mark gaps in lineage and ask the owner for evidence, not a guessed link from the name. Compare catalog upkeep, investigation time and connector coverage. Adopt if cross-team disputes recur and key definitions and edges can stay current. Fix names and definitions first for a single report.

Content note:This article is based on publicly available information and is intended as a reference for evaluating tools. Features, pricing, and related policies may change at any time; please refer to the latest official information.

Original source:www.alation.com