Lineage View - Dataflow > Data Source

[music43]

Hi

I am not sure what's going on here. I have noticed that when referencing a PBI dataflow it hard codes the workspace and flow GUIDs in the M script. While exploring a different method to bring in the dataflow, I was able to avoid the GUIDs and still access the data.

Now I have published these to the service, I noticed the lineage view has broken for the second method.

Original script (GUIDs)

Second method. I have a shorter version of the script but the outcome on the lineage view is the same.

Any idea what is happening?

Thanks

Oli

[v-chuncz-msft]

@music43 

Using the Navigation step might be the best practice. You may share feedback via Ideas to help improve Power BI.

[music43]

Hi @v-chuncz-msft 

Doesn't an update to the dataflow change the GUID? I know this could be overcome by parameterising them.

A small 'idea' like this would never make it to production as it would likely get lost on the ideas forum.

[jeffshieldsdev]

@music43 
Updates to dataflows won't change the GUIDs. Lineage view uses the GUIDs to identify workspaces and dataflows, which is why lineage view doesn't work without them. Linked Tables and Enhanced Compute Engine may not work without using the GUIDs either. 

GUIDs are more stable, I don't see Microsoft wanting to promote brittle identifiers like names.