Currently, the SourceDataFieldId column in the ViewFields table is only populated when using a "managed" (Add View) view — where it correctly references the DataField it maps to. For Custom Views, this column remains empty, even when the origin/source fields have been properly mapped within the view definition.
This creates a significant gap for anyone trying to build accurate, field-level data lineage directly from the repository. Since managed views are very limited in functionality (essentially just a select with aliases), most real-world projects rely heavily on custom views — which means the vast majority of field mappings are currently untraceable through SourceDataFieldId.
As a workaround, it's possible to reconstruct part of the lineage picture using a join across Views, ViewFields, DataFields, and DataTables, but this only exposes the current layer's structure — not the actual source field the custom view field is derived from. There is currently no supported way to retrieve the true upstream source field for a custom view field, even when it has been explicitly mapped.
Request:
We'd like to request a feature that populates SourceDataFieldId (or otherwise exposes an equivalent field-level source mapping) for Custom Views as well, not just managed views. This would allow lineage tooling built on top of the repository to accurately trace field origins regardless of the view type used.
