cachedEntity

[ebjim]

When I go to insert a dataflow as a source in another dataflow, I get this error:

There is no gateway involved as both dataflows live in the same workspace. Any ideas? Thanks in advance. 

[Ylreeb]

facing the same issue after creating a DFGen2 in Fabric using the "Import from PowerQuery template" function. Will cost my hours to fix this!!

[ebjim]

I have never created or named anything "cachedEntity". This error occurs when on any dataflow that is trying to use another dataflow as a source. 

[v-nikhilan-msft]

Hi @ebjim 
Apologies for the issue you have been facing. This might require a deeper investigation from our engineering team to properly understand what might be happening. 

Please go ahead and raise a support ticket to reach our support team:

https://support.fabric.microsoft.com/support
Thanks

[v-nikhilan-msft]

Hi @ebjim 
We havent heard from you on the last response and was just checking back to see if you got a chance to create a support ticket. If yes please share the details here. Otherwise, will respond back with the more details and we will try to help.
Thanks

[ebjim · Accepted solution]

@v-nikhilan-msft I have not filed a ticket because I am working around the issue. This is something that happens when I use a dataflow as a source inside another dataflow. I am avoiding that scenario for now. While it would be nice to have it resolved, I need to make headway on my project and time is limited.

[Element115]

Can you show us the M code for both queries?  I have 2 DFs, one being the source for another one.  And the data type of one column caused the Power Query engine to automatically insert a line of code that removed this column. Then when my code in the second DF tried to reference this column, I would get a similar error because the column didn't exist anymore because it had been removed from the first DF automatically by Power Query!

[ebjim]

@Element115 Unfortunately, I got rid of that DF.  So, I don't have anything that I can show.

[Element115]

OK... what about the error? Does it appear again with other DFs you are working on or was it a one-off?

[ebjim]

That was the only time a DF was used inside another DF. After the error, I stopped using that method. Had to find other workarounds to move forward.

[Element115]

Could you give me an idea what those workarounds might be?  Because I got a DFg2 that uses 2 lakehouse tables and a dozen of queries in reference mode and it causes a 'Dynamic datasources are not supported error.'

So I took out the queries that are in a reference chain and put them in their own DFg2. This led me to create 2 new DFg2.  In the main or final DFg2, I then connected to these 2 new DFg2s, ie used them as new sources.  But it didn't work, the same error keeps popping up.

Perhaps there is something in your workaround that might give me an idea.

[ebjim]

My situation did not involve the use of references the way you did. What I did was to create another lakehouse to house semi-curated tables.

[Element115]

Oh I see what you mean!  Basically, one chain of transformations into one DFg2 persisted to a lakehouse table. Repeat for all such chains.  Then in a final DFg2 just ingest the data from all these table as sources and you got a DF that will instantiate a semantic model for a Power BI report.

[v-nikhilan-msft]

Hi @ebjim 
Thanks for using Fabric Community.
Does the dataflow which you are trying to use as the source has any column named "cachedEntity"?

According to the error message, you might have some steps that reference the column 'cachedEntity' which has been removed or renamed or any other operation when you modified the query. It could be a step where you renamed, re-ordered columns, changed data types, removed other columns, etc.

Double-check the source dataflow to ensure the column "cachedEntity" actually exists. If it's not present, correct any typos or inconsistencies in the column name you're referencing. If the column was recently added or removed, refresh the source dataflow metadata in the destination dataflow.
Also try clearing the cache of your browser and retry again.

Hope this helps. Please let me know if you have any further queries.