HI @johanjsc , and @Marco_Polo_86 , @adeniranao , @Anonymous and @johanjsc
I've taken a look at this and can reproduce the error. However I think it is entirely consistent with Microsoft's PPU licencing. What I believe is happening is this:
User creates a PPU workspace (PPUW1) and generates a Dataflow on it from some data (PPUDF1)
User then connects to Dataflow PPUDF1 in Power BI Desktop and builds a Report visual from it.
User than publishes this Report to a non PPU Workspace (WS2).
This puts a Dataset and a Report on WS2. When the users sets up a refresh of Dataset on WS2 it fails with "Shared caller trying to read premium per user information" error.
I believe this is because you can't share Dataflows on PPU with Datasets on non-PPU. This is consistent with Microsoft's licencing. You can't share a Report on PPU with a non PPU user and you can't share a Dataset on PPU with a non PPU user, then why should you be able to share a Dataflow on PPU with non-PPU users ?
Dataflows on a PPU workspace get extra facilities, larger data storage, more refreshes, and linked entities etc. Why should you be able to share this with other non PPU users ?
The solution is to place the Dataflow on a non PPU workspace (this losing the benefits of PPU) or place the Report and Dataset on a PPU workspace (which onlu PPU licences can access.
I note there has been some mixed messaging on this from Microsoft and can't find any really clear statement of this. Perhaps someone at Microsoft could get Chris Finlan or someone to answer.
Hope this helps
Stuart
