Trace dependencies in Lineage

← Model

Lineage shows how tables, models, and metrics depend on each other, and where current Dashboards use those metrics. Use it before changing a definition to see what else would be affected, or to find where a metric’s numbers come from. Lineage needs the Explorer role or higher and shows only the current definitions.

Open Lineage

• On a metric or model page, read the calculation path in the side rail and select Open map for a wider view.
• Select View lineage on a table in Catalog.
• In an Explore result header, next to Where does this number come from?, select the metric’s Open map link, or use a Dashboard widget’s Lineage action, to follow the metric’s source.
• Direct Lineage links and the command palette remain available. Lineage is opened around a selected resource rather than from a sidebar item.

To focus on something else, choose Tables, Semantic models, or Metrics next to the search box and type its name.

Read the map and impact list

The map starts one step from the focused resource, with lanes for Table, Model, Metric, and Used in. Select the + next to a node to expand its next step. Selecting a node highlights its calculation path and dims other paths; Focus selected centers the map on that resource.

Pan and zoom with the map controls. Use the minimap to find your position in a larger map. Dashboard nodes link to the Dashboard that uses the connected metrics.

The Affects list below the map counts and names the affected definitions and Dashboards. A second line appears only when it adds something: the role the focus plays for a direct dependent, such as Numerator or Filter, or the definitions an indirect dependent goes through. The same list appears while editing (Affects if saved) and in the delete dialog. When the map is focused on a metric or model, the link above the title returns to its page. A shared entity name is a hint for model navigation, not a guaranteed join; see Link models.

Dashboard usage comes from the current saved Dashboard definition. It includes named semantic queries selecting the focused metric or a metric built from it. A model or table includes Dashboards using its downstream metrics. Drafts, past Dashboard runs, Explore runs, and Document Pages are not listed as usage.

See resource details

Select Show resource details to inspect the focus. Details show a table’s columns with types and keys, a model’s fields, or a metric’s calculation type, time grain, and inputs. Use Open metric, Open semantic model, or Open in Catalog to go to the resource itself. Metric and model pages show the calculation tree and available Slice by dimensions. A field expression containing a single column identifies that column; a more complex expression is shown as an expression rather than inferred column lineage. Details do not expose credentials or result data.

If Lineage is empty

No resources yet means the Workspace has no tables in Catalog and no semantic definitions. Select Open Catalog to choose tables, or, with the Editor role, Create semantic model. This resource isn’t available means it was deleted or you can’t access it; select Choose another resource.

With an agent

An Explorer or higher can read the same dependencies through workspace/lineage/relations, workspace/lineage/semantic-models, and workspace/lineage/metrics. Discover the Workspace with monomer_list using {"path":"workspaces"}, read workspace with monomer_read and the returned workspaceId, then follow availableOperations with a list limit from 1 to 100. Read a resource’s Lineage path to inspect its dashboardUsages: each item includes dashboardId, title, queryNames, and metricIds. These are the same current Dashboard usages shown in the app. Lineage describes current dependencies; it does not contain access decisions.