Schema Field Lineage

Know exactly where every API field comes from

API schemas evolve quickly, and it is easy to lose track of which contract fields map to which properties in your domain model. When a model property changes, you need to know which API fields are affected, and when an API field looks wrong, you need to trace it back to its source.

Field lineage solves this by creating a durable, inspectable link between each schema field and the model property it represents. This connection feeds into impact analysis, governance reporting, and data-flow visibility across your system.

What this walkthrough covers

This guided walkthrough shows you how to:

• Open a schema file and expand a field
• Open the Lineage section
• Search for a model property using the quick search
• Select a result to create the lineage mapping

The walkthrough uses an example schema called ProductApiSchema with a field called productName, and maps it to the Name property on the Product entity in the central model.

Step-by-step walkthrough

Click through the presentation below to follow each step. Each slide includes annotations highlighting the relevant area of the interface.

Next steps

Once lineage is established, you can:

• View lineage connections in the governance reports to see which API fields trace to which model properties
• Use impact analysis to understand how changes to a model property affect downstream schemas
• Add lineage notes to document any transformation or mapping logic between the source property and the API field