On-Prem execution not supported for entity... ...since it refers to another entity

[ChemEnger]

I know there are lots of other questions (and some answers) in the forum for this question.

I have a Dataflow (Fabric capacity workspace) with multiple queries, most of which are created using the same function to append matching tables from two other Dataflows, with some further combination (merging) where needed.

I have one query that is not refreshing on the service, with the error that it is referring to another entity.  As far as I can see, there is no real difference between the query marked with the red cross compared to that with the green tick, but the latter works while the former fails.

The green-dot queries have Enable Load turned on, whilst the amber-dot (...Prep) is turned off (I have also tried with it turned on).

I have tried following the success of @BugmanJ in Error: On-Prem execution not supported for entity" , including turning off Load for the red-cross query and using it only as a staging query - this also failed for the downstream query.

Edit:  I also tried splitting out the branching (the merge is to deal with some null records) into two separate queries, with Enable Load turned off, but this didn't work either:

Edit 2: I also tried bringing the merge up to the front of the query. No joy 😢

[BugmanJ · Accepted solution]

HI @ChemEnger ,

To note i am not using fabric but I had to do the following:

1) Have first query which is the main query. Ensure any columns meet the requirements to be stored (it can not be ABC123). Do nothing else. I call this "Original Data Query"
2) Reference the above query. in a new query, I call this "Data Reference Query". Do nothing else to this query

3) Create 3rd Query, Reference the above "Data Reference Query" as the source. Now do what you want with it.

Do this for each, i found i had a lot but had them in folders and thus avoided the problem. Are you using the 3 query mechanism?

[v-menakakota]

Hi @ChemEnger ,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.

Thank you,
Menaka Kota.

[v-menakakota]

Hi @ChemEnger ,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If the response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.

Thank you.

[v-menakakota]

Hi @ChemEnger ,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[BugmanJ · Accepted solution]

HI @ChemEnger ,

To note i am not using fabric but I had to do the following:

1) Have first query which is the main query. Ensure any columns meet the requirements to be stored (it can not be ABC123). Do nothing else. I call this "Original Data Query"
2) Reference the above query. in a new query, I call this "Data Reference Query". Do nothing else to this query

3) Create 3rd Query, Reference the above "Data Reference Query" as the source. Now do what you want with it.

Do this for each, i found i had a lot but had them in folders and thus avoided the problem. Are you using the 3 query mechanism?

[ChemEnger]

I did try this mechanism first of all, hence my linking to the thread.

I double-checked just now and am gettting exactly the same error.

Query 1 - Direct connection to another Dataflow, no steps other than navigation, all types correctly set

Query 2 - Directly references Query 1, no other steps, still correctly typed

Query 3 - Joins Query 2 to another query (simple, from a manually entered table, again correctly typed)

I can get the model (Gen 1 Dataflow) to work if I turn off loading for (1) but I would like it to be an output in its own right, as well as feeding (3)

[BugmanJ · Accepted solution]

Ah, I struggled to reference another dataflow and got similar errors. You will also find problems if the first one is updating and the second one wants to reference it. In the end, I now have several large dataflows that all use alot of the same "starting" parts and then just changed the end bits to suit. 

Where Gen2 are any better I dont know yet.

[v-menakakota]

Hi @ChemEnger ,

Thank you for reaching out to us on the Microsoft Fabric Community Forum.

Have you tried creating a new Dataflow from scratch and copying over the queries? This can help identify and eliminate any potential corruption or configuration issues in the original Dataflow.
Can you provide the full error message you’re encountering in the Power BI Service? This will help in identifying the exact cause of the issue.

[ChemEnger]

Hi,

I have now done a direct copy & paste of the entire set of the queries.  I still get the same error:

Error: On-Prem execution not supported for entity '[Query 3]' since it refers to another entity.. Param1 = [Query 3] Request ID: 3f48cb9e-8454-8b8d-de72-8eba4ddba04d.

It looks like I'll just have to make do with a disabled staging query, with an enabled direct reference as well as the joined query?