Is it possible to disable an entity in a dataflow from refreshing when the whole dataflow refreshes?

[Anonymous]

Hello I have a table, lets call it Table1 that contains millions of rows. I want to bring it into the cloud once as a dataflow and never refresh it.

Now i have another subset of this Table 1, lets call it Table 2, that I want to refresh everyday.

Table 1 and Table 2 are in the same dataflow. Is it possible to disable refresh on Table 1 but refresh Table 2 daily?

[jeffshieldsdev]

Yes, just put them in seperate dataflows.

[v-alq-msft · Accepted solution]

Hi, @Anonymous 

It is unsupported to disable an entity in a dataflow from refreshing when the whole dataflow refreshes. Here are some limitations and considerations.

Power BI Pro, Premium and Embedded workspaces:

• The linked entities feature is only supported among workspaces in the same storage account
• Workspace permissions do not apply to dataflows stored in Azure Data Lake Storage Gen2; only the owner of the dataflow can access it.
• Otherwise, all data prep features are the same as for dataflows stored in Power BI storage

There are some additional considerations as well, described in the following list:

• Once a dataflow storage location is configured, it cannot be changed.
• Only the owner of a dataflow stored in Azure Data Lake Storage Gen2 can access its data.
• On-premises data sources, in Power BI Shared capacities, are not supported in dataflows stored in your organization’s Azure Data Lake Storage Gen2.
• Each dataflow may use only one gateway. As such, all queries should be configured using the same gateway.
• Changing the gateway impact the entire dataflow.
• If several gateways are needed, the best practice is to build several dataflows (one for each gateway) and use the compute or entity reference capabilities to unify the data.
• Dataflows are only supported using enterprise gateways. Personal gateways will not be available for selection in the drop down lists and settings screens.
• There is a maximum of five referencing hops
• Cyclic dependencies of linked entities are not allowed
• The dataflow must reside in a new Power BI workspace
• A linked entity can't be joined with a regular entity that gets its data from an on-premises data source
• When a query (query A, for example) is used in the calculation of another query (query B) in dataflows, query B becomes a calculated entity. Calculated entities cannot refer to on-premises sources.

For further information, you may refer to the following links.

https://docs.microsoft.com/en-us/power-bi/service-dataflows-linked-entities

https://docs.microsoft.com/en-us/power-bi/service-dataflows-on-premises-gateways

Best Regards

Allan

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Anonymous]

Hi,

I see your solution is taking an approach from front end. Is it possible to do the same programmatically via. powershell?