Forum Discussion
Power BI Paginated Report Parameter Mapping Error
Hi govind_021 ,
I was able to reproduce this end to end using a simple repro setup. I used a disconnected Period table in a slicer, handled the MTD/QTD/YTD logic entirely through DAX, and mapped that same Period field to a paginated report parameter. This works correctly even without creating any physical relationships in the model.
In Power BI Desktop, the Paginated Report visual acts only as a parameter passing surface. It does not depend on the Power BI data model or relationships instead, it simply passes scalar values from Power BI to the paginated report. Because of this behavior, using a disconnected table for parameter mapping is valid and supported.
After adding a Date context to the report, the MTD, QTD, and YTD selections evaluated as expected in the Power BI visuals, confirming that the dynamic behavior is driven by DAX rather than relationships. At the same time, the paginated report correctly receives the selected parameter value, demonstrating that parameter mapping works independently of physical relationships.
Thank you.
Hi Rohit,
Thanks for your reply.
I’m still a bit confused about the issue. When I run the DAX query in the Query Designer in Report Builder, and pass the Calculation Group as a parameter there, it works completely fine and returns correct results.
The problem only appears when I embed the report in Power BI Desktop and try to map the parameters. At that point, the Calculation Group parameter shows a relationship error.
Also, the workaround you suggested is not very clear to me. Could you please explain it in more detail, maybe with an example?
Hii govind_021
The issue occurs only after embedding because Power BI Desktop requires the parameter source to be a physical table that exists in the model with actual rows. Calculation Groups are metadata tables, so Power BI cannot use them for parameter mapping. The fix is to create a small helper parameter table (e.g., YTD, MTD, QTD), map that table to the paginated report, and pass the selected value into your DAX query. This avoids the relationship error and keeps the logic intact.