Forum Discussion
Paginated Report Build using PowerBI Dataset
I have a Paginated Report setup that has a PowerBI DataSet as my DataSource.
That PowerBI Dataset has a Products table and a Regions table, with a 2-way (Cross-filter = Both)
relationship between the tables. When I review in this Dataset in the PowerBI Desktop, I see the
2-way Relationship working, so when a Filter is applied to Products, it limits the Regions values.
But in the Paginated Report, where I have a Dataset created using the Query Designer that uses the
Product field (From Products table) and the Region field (from the Regions table), and I apply
a Filter to the Product (Setting the Dimension/Heirarchy/Operation/FilterExpression) at the top
of the Query Designer, I see my Products values filtered but its still using all Regions. It looks
like a full outer join result.
So I was originally assuming that the relationships in the PowerBI dataset would apply in Pag. Reports,
but its not looking like this is true. And I'm also have not been able to find any discussion or doc
on this.
Can anyone confirm that the relationships do not work in Pag. Reports?
Or have I set something up incorrectly and they really do work?
Any workarounds others are using?
Any feedback is of course appreciated. Thanks in advance.
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.
9 Replies
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.
This still seems to be an issue as of 4/26/21.
