Linked Entities on Pro Workspace

[PPStar]

Hello. 

I have a premium workspace and i need to share some dataflows (with resticted columns and filtered data) with some Pro Users. 

Please can someone tell me if this is a supported solution and the pro /cons and assumptions, if any

1. I create a Linked Entity Dataflow in my Power BI Pro Workspace which is linked to my premium workspace dataflow

2. In my pro workspace, I perform ETL on the linked entity such as filtering data and removing columns

3. I then reference the linked entity. 

4. I then disable load on the linked entity

5. This leaves me with the referenced table which has all the filtered data and less columns . 

I did a test and this solution works. 

Is this supported?. In what scenarios will this not work, for e.g. if on the premium workspace i enabled the enhanced computer engine or implement Incremental refresh, will this soltuion still work?

[rajendraongole1 · Accepted solution]

Hi @PPStar - Yes, the solution you described is supported, but there are important factors to consider regarding capabilities and limitations.

Creating a Linked Entity in a Power BI Pro Workspace: You are creating a linked entity dataflow in a Pro workspace that references a dataflow in a Premium workspace. This is a valid approach to share specific dataflow entities across workspaces, though there are some limitations on functionality when it comes to Pro versus Premium features.

Performing ETL in Pro Workspace: Performing transformations (such as filtering and removing columns) is fully supported in linked dataflows, and these transformations only impact the Pro workspace where you are creating them.

Disabling Load on the Linked Entity: Disabling load on the original linked entity to use only the referenced version is a standard Power Query technique, which is helpful in keeping the data model optimized.

your approach is supported and works for scenarios where restricted access is required for Pro users. However, performance limitations, data refresh constraints, and the inability to use features like incremental refresh or the enhanced compute engine may limit scalability.

Solved: Linked Dataflows - no option to add linked entity ... - Microsoft Fabric Community

Link tables between dataflows - Power Query | Microsoft Learn

Solved: Re: Incremental refresh restrictions? Pro License? - Microsoft Fabric Community

Hope this helps

[PPStar]

Thank you so much for your help. 

What other contraints and limitations am i bound to. 

At the moment, all my dataflows in my premium capacity are not really using any premium capabilties, such as IR, compute entities.. They are simply just an interface to the SQL backend (just imports from sql into a dataflow)

What other premium features should i be concerned about that wont work in the Pro workspace?

[rajendraongole1 · Accepted solution]

Hi @PPStar - Yes, the solution you described is supported, but there are important factors to consider regarding capabilities and limitations.

Creating a Linked Entity in a Power BI Pro Workspace: You are creating a linked entity dataflow in a Pro workspace that references a dataflow in a Premium workspace. This is a valid approach to share specific dataflow entities across workspaces, though there are some limitations on functionality when it comes to Pro versus Premium features.

Performing ETL in Pro Workspace: Performing transformations (such as filtering and removing columns) is fully supported in linked dataflows, and these transformations only impact the Pro workspace where you are creating them.

Disabling Load on the Linked Entity: Disabling load on the original linked entity to use only the referenced version is a standard Power Query technique, which is helpful in keeping the data model optimized.

your approach is supported and works for scenarios where restricted access is required for Pro users. However, performance limitations, data refresh constraints, and the inability to use features like incremental refresh or the enhanced compute engine may limit scalability.

Solved: Linked Dataflows - no option to add linked entity ... - Microsoft Fabric Community

Link tables between dataflows - Power Query | Microsoft Learn

Solved: Re: Incremental refresh restrictions? Pro License? - Microsoft Fabric Community

Hope this helps

[PPStar]

Thanks for your response. 

So, on my premium workspace dataflow, i have the enhanced compute engine set to ON. 

I am still able to connect to this dataflow from my pro workspace and do ETL etc?

 I have not used Incremental refresh yet, but i am assuming enabling IR on the premium dataflow will limit this solution and i would not be able to us the dataflow in the pro workspace?

[rajendraongole1 · Accepted solution]

Hi @PPStar - Yes, you are correct.If Incremental Refresh is a critical feature for your scenario, you might need to consider an alternative strategy, such as using a dedicated Premium workspace or Premium Per User (PPU) license for the Pro users who need access to the dataflow with Incremental Refresh enabled.

Enhanced Compute Engine ON: Your solution works, and Pro workspaces can connect and perform ETL on the linked entity.

Incremental Refresh ON: Pro workspaces will not be able to use or link to this dataflow once Incremental Refresh is enabled.

If you enable Incremental Refresh on a dataflow in the Premium workspace, this will create a limitation for Pro users trying to access that dataflow. Incremental Refresh requires the Premium capacity to process data in a staged way and handle large data volumes, and because this feature is exclusive to Premium, Pro workspaces won’t be able to consume dataflows that have Incremental Refresh enabled.

In other words, once you enable Incremental Refresh in the Premium workspace dataflow, you likely won’t be able to use that dataflow as a linked entity in a Pro workspace. This is because Pro workspaces lack the capacity and capabilities needed to process dataflows with Incremental Refresh.

Hope the above details works