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
Separate Download and Publish Permissions for Power BI Workspaces
Idea / Feature Request Introduce more granular permissions in Power BI to independently control report download and report publishing permissions at the workspace level. Business Scenario We have ...ewarstdhyjugkhi1 hour agoMicrosoft EmployeeNew17Views8likes0CommentsSupport Fabric SQL Database with workspace-level inbound Private Link
Fabric SQL Database supports tenant-level Private Link but not workspace-level Private Link. Securing a small number of databases therefore requires enabling Private Link across the entire tenant, in...WorkFull222 hours agoAdvocate INew30Views1like1CommentPaste values in slicers for hierarchy data
Hierarchical slicers are widely used in enterprise reports (for example Product RCN > SKU Key, Region > Country > City, or GPP > Division > RCN > SKU). Users often need to bulk-filter by pasting valu...eddieisking20004 hours agoFrequent VisitorNew0Views0likes0Comments