cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Advocate III
Advocate III

Dataflows: Error: On-Prem execution not supported for entity

I'm encouting an error when using dataflows;

 

Error: On-Prem execution not supported for entity 'REDACTED/Rant&RaveGlobal' since it refers to another entity... RootActivityId = REDACTED.Param1 = REDACTED/REDACTED/Rant&RaveGlobal Request ID: 71958418-b401-ea01-b1be-98a685669190.


I know why I'm getting the error but I just want to know if I can work around it otherwise dataflows seems extremely limited.

 

I have a two dataflows currently. Lineup and Surveys.

 

  • Lineup contains two entities Lineup and GlobalSalesforceIds.
    • Lineup lists employees and what team they were on when, the unique key in this entity is EmployeeNumber-Month, e.g. 12345678-43374.
    • GlobalSalesforceIds contains the EmployeeName, GlobalSalesforceID and the EmployeeNumber the unique key in this entity is GlobalSalesforceID, some employees can have many Global Salesforce ID's so I cannot put them in the Lineup entity.
    • All the data in this dataflow is obtained from cloud sources, SharePoint and Salesforce, so no need for an on-prem gateway.
  • Surveys contains entities form three different data sources.
    • The EmployeeNumber is present in two so I can create a column that contains the EmployeeNumber-Month key so I can link back to Lineup when building reports.
    • The third entity, Rant&RaveGlobal, uses the GlobalSalesforceID of the employee and does not contain the EmployeeNumber.
    • All the data in this dataflow is obtained from on-prem sources and therefore uses the gateway.

What I therefore want to do is add the GlobalSalesforceIds entity from Lineup as a linked entity in Surveys and then merge the two so I can pull the EmployeeNumber and create a column for the EmployeeNumber-Month key.

 

I can achieve this but it means removing the gateway while linking the entity and then re-selecting it. So obviously the issue is that the linked entity cannot use the gateway but is there a way around it? Otherwise dataflows seem very limiting in that you cannot refresh data from cloud and on-prem data sources.

1 ACCEPTED SOLUTION
Advocate III
Advocate III

As is customary with these situations, I spend time writing a question with an example and then I discover the answer.

 

The answer in this case was to untick the Enable load option on the linked entity.

 

I've tested a on demand refresh and scheduled and both worked.

View solution in original post

6 REPLIES 6
Regular Visitor

I get the same error message.

 

In query 1,  I am calling a function to return a value from a table populated by query 2.

when I remove the function the dataflow refreshes correctly,  using the function query 1 fails with the error as above.

 

any ideas for a work around?

 

Advocate III
Advocate III

As is customary with these situations, I spend time writing a question with an example and then I discover the answer.

 

The answer in this case was to untick the Enable load option on the linked entity.

 

I've tested a on demand refresh and scheduled and both worked.

View solution in original post

Hi @mark_carlisle ,

 

I faced the same situation using one entity as parameter in my dataflow to another entity in the same dataflow, and received this error message.

 

Actually I need to enable loading of that "parameter entity" for further usage. But after reading your solution, I did a workaround by disabling the loading of the "parameter entity" and create a new entity simply by linking the previous "parameter entity" and then the refresh works, although practically they are the same!

 

It is strange that by enabling the loading of the linked entity the dataflow refresh does not work. Is it planned by Microsoft to be like that?

 

 

Best regards,

cyongt_bdf

Anonymous
Not applicable

I am glad you took the time to come back and tell us what sorted the issue, because this has just helped me.

Could I just confirm, is scenario still working for you? It worked for me until around Dataflows went to General Availability and now does not.

Anonymous
Not applicable

@mark_carlisle It does work for me.

Helpful resources

Announcements
secondImage

Happy New Year from Power BI

This is a must watch for a message from Power BI!

December Update

Check it Out!

Click here to read more about the December 2020 Updates!

Community Blog

Check it Out!

Click here to read the latest blog and learn more about contributing to the Power BI blog!

Get Ready for Power BI Dev Camp

Get Ready for Power BI Dev Camp

Mark your calendars and join us for our next Power BI Dev Camp!.

Top Solution Authors