Forum Discussion
Power BI Desktop with Premium Dataflow
I have a Dataflow that makes 2 x API JSON calls and then appends the two queries as new. The Dataflow works exactly as I expect and I can see the data. The appending of the data required me to upgrade the Workspace to Premium. When I connect Power BI Desktop to the Dataflow I get the error below. I have changed my Power BI Licence from Pro to Premium per User.
ProPlusInformationNotAllowedForNonProPlusCaller: ProPlusInformationNotAllowedForNonProPlusCaller
Details:
Error=ProPlusInformationNotAllowedForNonProPlusCaller
RequestId=3e75b98d-c1d1-4a6d-a406-6492ea2a379c
RequestUrl=https://wabi-uk-south-redirect.analysis.windows.net/metadata/v201606/cdsa/dataflows/f4f895e6-2b32-4e3f9711-5ac7dcc61296/storageAccess
2 Replies
- AnonymousNot applicable
Hi graemeg ,
Check this topic https://community.powerbi.com/t5/Service/Not-allowed-to-load-dataflow-into-power-bi-desktop/m-p/1700928
Looks like the problem might be sloved by removing the workspace from Premium PPU.
Best Regards,
Jay
- graemegFrequent Visitor
This solution does not work. I have been through the whole process again and there is definitely an issue. The workspace I am using has to have PPU Capacity in order to merge the results from two API calls. The data refresh within the Workspace works exactly as expected. When I upgrade the workspace to PPU capacity I got the following message:
"Only people who have Premium Per User licences will be able to access this workspace if you make this change".
I then made sure that I have Premium Per User licence (I am the admin) and I still keep getting the following message from Power BI desktop when I try to connect to the Dataflow:
ProPlusInformationNotAllowedForNonProPlusCaller: ProPlusInformationNotAllowedForNonProPlusCaller
Details:
Error=ProPlusInformationNotAllowedForNonProPlusCaller
RequestId=df69552e-ec2e-4e8b-b6bd-c17a7d43a2d7
RequestUrl=https://wabi-uk-south-redirect.analysis.windows.net/metadata/v201606/cdsa/dataflows/f4f895e6-2b32-4e3f-9711-5ac7dcc61296/storageAccessSomething not right in the Microsoft environment.