> For the complete documentation index, see [llms.txt](https://docs.paradime.io/app-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.paradime.io/app-help/products/dino-ai/tools-and-features/column-level-lineage.md).

# Column Level Lineage

The Column-Level Lineage Tool allows DinoAI to trace how individual columns flow through your data pipeline, giving you precise visibility into data dependencies directly from the Code IDE.

This tool lets DinoAI answer questions about where a column originates and what it feeds into downstream, so you can understand data provenance and assess the impact of changes before you make them.

#### Capabilities

The Column-Level Lineage Tool exposes a single underlying operation:

**get\_column\_level\_lineage** fetches the full lineage graph for a specific model and column combination. It returns a JSON structure of nodes and edges, each carrying the file path, model name, column name, and upstream or downstream direction. Requests time out after 60 seconds.

#### Using the Column-Level Lineage Tool

1. Open DinoAI in the right panel of the Code IDE
2. Provide the model name and column you want to trace
3. Add your prompt describing what you want DinoAI to do with the lineage results
4. Review DinoAI's findings and apply them to your development work

#### Example Use Cases

**Tracing a Column's Upstream Sources**

**Prompt**

```
Get the column-level lineage for the revenue column in the fct_orders model.
```

**Result:** DinoAI fetches the full lineage graph for that column, identifying every upstream model and source that contributes to it so you can understand data origin and spot potential issues.

**Understanding Downstream Impact**

**Prompt**

```
Show me what depends on the customer_id column in dim_customers.
```

**Result:** DinoAI maps the downstream nodes in the lineage graph, surfacing every model and column that would be affected by a change to that field.

#### Working with Other Tools

The Column-Level Lineage Tool works well alongside DinoAI's other capabilities to support your full development workflow:

* Combine with the **Catalog Search Tool** to first discover the right model or column, then trace its lineage
* Combine with the **SQL Execution Tool** to validate query logic against columns you've traced through lineage
* Combine with the **Google Docs Tool** or **Notion Tool** to cross-reference lineage findings against your data modeling specs
* Use alongside **Git Lite** to commit and push lineage-informed changes before opening a pull request

#### Best Practices

**Be specific with model and column names** — Provide the exact model name and column name to ensure DinoAI retrieves the correct lineage graph.

**Account for refresh cadence** — Lineage data reflects the latest `manifest.json` and `catalog.json`, so very recent changes may not yet appear.

**Verify complex graphs** — For models with many upstream dependencies, review DinoAI's lineage summary carefully before making structural changes.


---

# 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:

```
GET https://docs.paradime.io/app-help/products/dino-ai/tools-and-features/column-level-lineage.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.