Forum Discussion

hs28's avatar
hs28
Advocate I
1 year ago

Paginated Power BI Report

Hi, We’ve created a Paginated Report using the existing semantic model of a Power BI report. This Paginated Report was built in the Power BI Service and embedded as a visual on the second page of th...
Need Help
rajendraongole1's avatar
rajendraongole1
Super User
1 year ago

Hi hs28 - can you check if the problematic slicer value exists exactly as it appears in both the Power BI report and the Paginated Report dataset. Even minor differences in spelling, spaces, or casing can cause issues.If your dataset has different sources or transformations, verify that this value isn’t being altered before being used as a parameter.

 

check if the parameters are associated with slicers, Set to accept multiple values if it should.Using the correct data type (e.g., text vs. integer).Fetching values correctly from the dataset.Adding a filter to remove blanks in Power BI.
Using IF(ISBLANK([Field]), "N/A", [Field]) in DAX to replace nulls.

 

Since parameters are passed via URLs in the embedded Paginated Report, certain characters (&, %, /, etc.) might break the URL encoding.
If your problematic value contains special characters, try renaming it temporarily (e.g., replacing spaces with underscores) and see if that fixes the issue.