Check your eligibility for this 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700.
Get StartedDon't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.
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 the existing Power BI report.
Here’s how the setup works:
Page 1 of the Power BI report: Displays the data in a table format and uses slicers for filtering.
Page 2 of the Power BI report: Contains the Paginated Report, which uses the slicers on Page 1 as parameters.
Everything functions as expected: the slicers on Page 1 are synced with the parameters on Page 2. However, we’re encountering an issue where one specific value from one of slicers isn’t being passed correctly as a parameter to the Paginated Report.
All other slicer values sync perfectly, but this one value always fails to work as expected. We’re unsure what might be causing this issue and would greatly appreciate any insights or suggestions.
Thank you in advance!
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Prices go up Feb. 11th.
If you love stickers, then you will definitely want to check out our Community Sticker Challenge!
Check out the January 2025 Power BI update to learn about new features in Reporting, Modeling, and Data Connectivity.
User | Count |
---|---|
144 | |
75 | |
63 | |
51 | |
48 |
User | Count |
---|---|
204 | |
86 | |
62 | |
59 | |
56 |