Forum Discussion
Paginated Report Build using PowerBI Dataset
I did open Ticket with Microsoft and did get an answer from them.
The PowerBI Dataset Relationships are not supported when accessed from
Paginated Report Builder. There are two suggested ways to work around these
are to either rely completly on Measures from a PowerBI DataSet, or do setup
a Derived table by creating new Table using a DAX table funcion like FILTER.
And then relying on this single table for the Pag.Report. In my case, I needed both
of these ideas. I created a Drived table using FILTER to limit my main Fact table as needed.Then I can to create the various Measures needed in this FILTERED table to be used by the report.
It works, but looking forward to the future when this can be done much easier.
Hi dclmorr
Sorry I can't repro your issue on my side, please kindly raise it to support team for better advice. thanks!:
https://powerbi.microsoft.com/en-us/support/
Thanks for the response v-diye-msft . I've made a small Repro case and put the files on a OneDrive share.
For the PBIX, you will see its Filtered to the BusinessUnit "Energy - Package". And has a filter on Location "A1*".
Because of the BusinessUnit filter, the only value shown is "A142".
And then in the RDL, if you'll open the QueryDesigner you see a BusinessUnit filter set to "Energy - Package" just
like the PBIX. And there is a Parameter added to the report for LocationName. If you run the report, you can
select the LocationName parameter list and you'll see a large number of "A1*" values to select from, so it is
NOT limited to just "A142" like the PBIX implementation is. So I'm assuming this means that the Relationship
defined in the PBIX is not being used in the RDL that references this published PowerBI Dataset.
I have to guess this is just a basic misunderstanding on my part as to how an RDL dataset works when using the
PowerBI published data as the DataSource but I'd like to understand why. Or of course if I'm just doing something
incorrectly and it can work that would be great.
I did open Ticket with Microsoft and did get an answer from them.
The PowerBI Dataset Relationships are not supported when accessed from
Paginated Report Builder. There are two suggested ways to work around these
are to either rely completly on Measures from a PowerBI DataSet, or do setup
a Derived table by creating new Table using a DAX table funcion like FILTER.
And then relying on this single table for the Pag.Report. In my case, I needed both
of these ideas. I created a Drived table using FILTER to limit my main Fact table as needed.Then I can to create the various Measures needed in this FILTERED table to be used by the report.
It works, but looking forward to the future when this can be done much easier.
I faced the same issue, as I make a heavy use of dimension tables in PowerBI Desktop. At first, I thought that PowerBI Report Builder would work with the relations between the tables, but I saw that it is not the case thanks to this thread (after weeks of wondering what I was doing wrong).
The solutions proposed here work, but I find this to be an ugly workaround.
Is there any plan from Microsoft to actually support the relationships when connecting PowerBI Report Builder to a PowerBI data source? That would be a HUGE step forward and would totally make sense as those 2 tools should be as integrated as possible.
I agree Anonymous , I would really like to see better integration from Microsoft also. For other Paginated reports I've had to make I have had to forsake any PowerBI integration and I'm back to just using Paginated reports via direct SQL queries just like it was a SQL Report server report. With all the progress that PowerBI provides, to have to resort to the very old style reports for Paginated reports seems very strange.