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.
can you help me with pbix where you have implemented it with any dummy data , just to understand the workaround ?
Hi govind_021 ,
Thanks for reaching out to the Fabric Community Forum.
This issue comes up because Power BI Desktop cannot use a Calculation Group to pass values into a paginated report, since a calculation group does not have actual data rows that the Paginated Report visual can read. An easy workaround is to create a small table manually using Enter Data with values like YTD, QTD, and MTD, and use this table (PeriodParam[PeriodName]) in your slicer and also for parameter mapping. After that, create a measure like Selected Period = SELECTEDVALUE(PeriodParam[PeriodName]) and write your YTD/QTD/MTD logic using a SWITCH statement based on this measure. Finally, when the .rdl file is uploaded to a Premium or Fabric workspace, you can map the report parameter (for example, @Period) to PeriodParam[PeriodName] inside the Paginated Report visual. This method works because the physical table has real values that Power BI can pass into the paginated report, whereas a calculation group cannot be used for this type of parameter connection.
Thank you.
Hi govind_021 ,
I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you
Hi govind_021 ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions
But that table will still be disconnected how do i connect it to the other tables.
It requires valid physical relationship between tables , we cant pass filters through dax otherwise how would the dynamic slicing work.
it would be of great help if you can provide the sample file with dummy data with the approach you are suggesting.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 govind_021 ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions