Forum Discussion
Paginated Reporting / Power BI Premium Per User License
- 5 years ago
Hello Amerikaner !
This works fine for me, I have worked with my power BI service hosted datsets connected live with a Premium per User workspace. It works the same way it works with Power Bi Desktop ,I only had to enable XMLA Read Write on my Power BI tenant .
I am able to use DataSOurce -->Add Power Bi Datset Connection and it works seemlessly from there.
And If you want to use your local power BI dataset, then please open up your PBix file that contains the dataset on local and then copy the port name from DAX studio or local folder (you may find that on web how to get that) . Now use this to connect to "SQL Server Analysis Services" connection :
You are good to use your paginated with this datasource creating the datsets on this ! Only issue is that you will need to keep your PBIX running and also if you choose to close it /restart machine then change the datsource to new port/select new DB that appears on new Pbix open.
Thanks!
Abhinav Singh
Hmm... This may be teh same reason that MS is investigating.
Just to confirm you did select dataset in options?
 
I just now selected options and selected both default and then browse server.
 
 
Unsuccessful.
- AbhiSSRS5 years ago
Solution Sage
Hmm... Lets leave it to MS then ! Please do post here what they find when this is resolved! 🙂
Thanks!
- Amerikaner5 years ago
Helper I
Hi Abhinav,
I found the solution and must give credit to Peter Myers (Bitwise Solutions) and Chris Finlan (Microsoft) as I followed their XMLA end point process from the Power BI Paginated Reports in a Day Series,Video #15 (Visualizing Report Data - Part 2, Begin Marker 1:20 | End Marker 2:30.
Two discoveries: 1) Do Not Select "Add Power BI Dataset Connection", Do Select "Add Data Source", then Select "Microsft SQL Server Analysis Services" and 2) Under Data Source Properties / Credentials, Select "Do Not Use Credentials". This fixed the issue for me. Screenshots below.
 
 
 
 
  
 
- AbhiSSRS5 years ago
Solution Sage
I do get this error only when I disable my XMLA Endpoint ReadWrite (which i guess you already have enabled)
- AbhiSSRS5 years ago
Solution Sage
Alright this got on my nerves lol! Did some changes with Admin portal and got to replicate with another setting which makes sense! Please go and check if this too is enabled for your tenant! As I see your datasets are also from on-prem so below setting is required.
Please mark as solution if this is it! 🙂
Thanks!
Abhinav Singh