Skip to main content
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Join us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.

Slider141

Slicer values not passed as bind parameter values when using Power BI template (New Issue 2025)

Submitted by on ‎01-09-2025 07:44 PM

Hi,
Since returning from Christmas leave we have noticed slicer visual parameters are no longer working when building new PBI reports using a previously published Power BI semantic model (which has the parameters and bind varibles set in the published semantic model). These bind variables are passed through to Snowflake SQL query, but are no longer work when creating slicers in the report (only pass through the default values now). 

Prior to Xmas we could use our Power BI template to build reports and connect to the Power BI Semantic Models published in the online service and the slicer values were passed to Snowflake. These previously published reports are still working in the online service and if we download these and open in the desktop client they are also still working?

We are using the Power BI Desktop Version: 2.130.930.0 64-bit (June 2024).

Has anyone experienced something similar, or have any suggestions? 
Were there any updates to the Power BI Online service recently that may have caused this?

Thank you for any guidance or suggestions to fix this issue. Cheers.


 

Status: Investigating
See more ideas labeled with:
2 Comments (2 New)
Comments
Anonymous
Not applicable
‎01-09-2025 09:51 PM

Hi,@Slider141 .I am glad to help you.
By slicer visual parameters, do you mean field parameters?
Use report readers to change visuals (preview) - Power BI | Microsoft Learn

vjtianmsft_0-1736487979407.png

Please make sure that the slicer is set to interact with all relevant visual objects.
If my understanding is correct, could you please try deleting the originally created parameter and recreating the field parameter to see if that solves the problem.
If the problem persists after trying these actions, please contact Microsoft Support and provide more detailed error information (including screenshots that do not contain sensitive data, etc.) to check if this is indeed an issue, thank you for your support.
URL:

Microsoft Fabric Support and Status | Microsoft Fabric


 

vjtianmsft_1-1736488250700.png
I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
Best Regards,
Carson Jian

Slider141
Regular Visitor
‎01-12-2025 03:27 PM

Thank you for your response and suggestions.
These options did not fix the issue, so I have raised a Power BI Support call as you have suggested.
Kind regards.

Idea Statuses