Error: On-Prem execution not supported for entity"

[BugmanJ]

Hello All,

A rather fustrating problem this. I have two dataflows, both using the same connections, both been working just fine for months.

I had to change one of them recently, basically inside the flow, I pull in an SQL query, adjust it, and then add in a static data query, basically an extra line and its this line i had to edit.

Now when I try to refresh this dataflow, its gives me the usual error:

Error: On-Prem execution not supported for entity 'XXXXX/YYYYY/Name of Query since it refers to another entity.

That other "entity" is a static table thats been there for months. Its the same table as in the other dataflow which continues to work just fine, even after applying the edit.

I have tried:

• Turning off "enable load"
• Adding in a fresh table as another connection
• adding in another connetion
• deleting and adding the connection

So right now I am just stuck. I have even tried exporting the JSON and reimporting under a different name, only to be met by the same error. What is so fustrating is that the other flow is just fine, doing the same thing.

What can be done to correct this error?

Thanks

[BugmanJ · Accepted solution]

So actually, this is quite an easy answer, and doesnt require turning off loads.

In Short, do the following:
Query 1 (Data Pull) - This is main data pull in query. Do as little as needed to the data (normally ensure that all columns are in a data format). Do nothing else.
Query 2 (Data Pull Reference) - Create a reference to the above Datapull, do nothing, but ensure its well labelled. This is what your going to use for further queries

Query 3 (Main Query) In this query, make a reference to the above Query 2 and then do all your maniupulation. Any other queries you need to bring in, ensure you have done the the other two queries, so all  you are bringing in is a referenced query.

Works a like a dream.....

[v-karpurapud]

Hello @BugmanJ

Thank you for reaching out to the Microsoft Fabric Community.

Thank you @GilbertQ for your prompt response.

The error "On-Prem execution not supported for entity" typically occurs when a dataflow references another entity that requires an on-premises gateway, but the gateway settings are not properly configured or supported for the specific entity.

1. Make sure the gateway settings for the dataflow are correctly configured. If the gateway is locked, you may need to edit the dataflow settings to unlock it.
   
   
2. Add an entity from another dataflow using the Power BI dataflow connector. When prompted to switch to Power BI dataflow mode, accept and proceed. After adding the entity, you can delete it. Save the changes and refresh the dataflow.
   
   
3. Untick the "Enable load" option on the linked entity. This has been reported to work for similar issues.

If my response has resolved your query, please mark it as the Accepted Solution to assist others. Additionally, a 'Kudos' would be appreciated if you found my response helpful.

Thank you!

[BugmanJ]

Actually this didnt help me at all, but see the next post for an easy solution!

[GilbertQ]

Hi @BugmanJ 

What happens if you remove the static table, see if it refreshes successfully.

If that works, go back in and add back the static table?

Also could you not create a SQL Query which would be the static table?

[BugmanJ]

I have solved it, see below, but for further learning, how do you access a static table built in a query via SQL?