Forum Discussion
Dataflows, multiple workspaces, and Power BI Embedded - where to assign capacity?
that is a very unfortunate setup. The dataset chaining issues are already bad enough, but now you add dataflows and embedded into the equation too. It's as if you are trying to find the most complex setup imaginable.
Maybe you can revisit your requirements and combine workspaces A and B?
Think of this in terms of "Import Mode" versus "Direct Query Mode". The dataflows in A are in Import Mode - nothing you can change there. The datasets in B are in import mode too - again nothing you can change. The datasets in C are in Direct query mode, which means they don't really consume resources in C. So you could make C really skinny but need to make B rather beefy. We haven't yet figured out how dataflow size actually reflects on a capacity. Documentation on that seems to be scant.
Hi lbendlin
Thanks for your input. We have the setup in A because other users make use of the dataflows for other reports in other workspaces.
To make it less complex, I can combine B & C so they are in a single workspace. Would I still need to assign capacity to A or can I get away with assigning it solely to the single workspace (B+C)?
The idea of a shared ("golden") dataset is that you prepare the data once, and then use it against many different audiences. You should combine A+B, not B+C.