Add dataflow entity from another dataflow

Dedicated support for the following workflow should be a priority.

Currently there are a bunch of hacks people are resorting to to disable entity loads. But this and my workflow should be dedicated features.


It follows on, extends the hack to disable loading of a dataflow entity to use it as reference logic. e.g. a master data transformation/ETL scenario.

I've recently found that you can ammend the M query in a dataflow entity to reference an entity from another dataflow via entering the workspace directly.

I discovered this by testing whether the copied M query from PBI desktop of a dataflow entity could be pasted into the query editor of a different dataflow in power bi service. It seems to work.

Just another deficit and hacky nature of Power BI that I find annoying.... they are still not supporting metadata management and content reuse as a first class capapbility...

I think there should be a dedicated option to add a workspace and an entity from another workflow directly.

So Im concerned and wouldn't be surprised if the dataflow ETL that I built today will be invalidated in the future...
So by example the code in BI service in a dataflow looks like below.
Once the dataflow param is set to null and the workspace connects to your workspace ID you can then navigate the various dataflows.
By disabling load as others have found you can then start to maintain a core registry of logic in a stage area and resuse more widely. This is getting a lot closer to adequate re-use of code and logic.

let
Source = PowerBI.Dataflows(null),
#"1234" = Source{[workspaceId = "1234"]}[Data],
#"5678" = #"1234"{[dataflowId = "5678"]}[Data],
CIRAM_STG_tblVehicle = #"95678"{[entity = "CIRAM_STG_tblVehicle"]}[Data],
#"Renamed columns" = Tabl.RenameColumns(CIRAM_STG_tblVehicle, {{"fldRegistrationNo", "Rego"}})
in
#"Renamed columns"