Lineage view issue for dataflow when a manually created Mashup query.
There is a lineage view issue when a manually created Mashup query is used to build a semantic model that connects to a dataflow.
The document mentioned that lineage between semantic models and dataflows is not guaranteed if a manually created Mashup query is used to connect to the dataflow.
Lineage in Fabric - Microsoft Fabric | Microsoft Learn
When connecting to the dataflow on the desktop and using the Power Query advanced editor, I tried entering the dataflow name and workspace name instead of the dataflow ID and workspace ID before publishing. However, they were unable to see the dataflow in the lineage view.
The customer requested a feature that allows the mashup query, which includes the dataflow name and workspace name and publishing it to display the lineage view correctly.
Recent ideas
Data Pipelines - Run only selected activities
For debugging and testing pipeline activities during development, allow us to select one or multiple activities and run only the selected pipeline activities. For example, I'm working on editing ...frithjof_v9 hours agoCommunity ChampionNew613Views11likes2CommentsSemantic model connection bindings should be in source control (Git)
Semantic model data source connection bindings should be source controlled. A semantic model can contain multiple data source references, each of which can be mapped to a separate Fabric data connec...frithjof_v16 hours agoCommunity ChampionNew17Views1like0CommentsBulk changing column names in Visualizations Pane
We often use raw/api column names or measures with a set nomenclature to be consistent and to keep track of them but we do not want to display these names in the visuals. Currently we have to change ...vishal14019720 hours agoFrequent VisitorNew6Views0likes0Comments