Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

The Power BI Data Visualization World Championships is back! It's time to submit your entry. Live now!

Reply
Aacuabo
New Member

Power BI Dynamic Query Binding Issue: Slicer Not Refreshing Data + Mysterious '?' Icon

Hey Power BI gurus,
I'm hitting a wall with dynamic query binding for a large SQL source.
The Goal: Use a Slicer (from a separate CalendarTable) to pass a date value to a Power Query Parameter, which then filters the large SQL table.
What I Did:
Created a PQ Parameter (p_SelectedMonthYear).
Used the parameter in my SQL query (works great in Advanced Editor).
In Model View, I bound the Slicer column (MonthYearForSlicer) to the parameter.
The Problem:
Moving the slicer does not refresh the data in the visuals.
The column I used for the binding in the Model View has a small question mark (?) icon next to it.
My Key Questions:
What does the question mark (?) on the bound column signify?
Is there a common reason the visual refresh is failing (data type mismatch, security settings, etc.)?
Any quick troubleshooting tips on this mysterious '?' or why my dynamic binding isn't working would be awesome!

2 ACCEPTED SOLUTIONS
MFelix
Super User
Super User

Hi @Aacuabo ,

 

The question mark (?) is the symbol that the specific field is a dynamic binding to the query you can see that on the documentation:

MFelix_0-1765900894168.png

What is the type of model you are using Import or DQ?

 

Be aware that for the dynamic binding to work the Fact table needs to be DQ and the dimension needs to be import or Dual model, creating a composite model.


Regards

Miguel Félix


Did I answer your question? Mark my post as a solution!

Proud to be a Super User!

Check out my blog: Power BI em Português





View solution in original post

Zanqueta
Super User
Super User

Hi @Aacuabo

 

Dynamic query binding in Power BI can be tricky, especially when working with large SQL sources.

1. What does the question mark (?) icon mean?

The ? icon next to the bound column in Model View indicates that the binding is not fully validated. Common reasons:
  • The parameter is not correctly linked to the field.
  • The data type of the slicer column does not match the parameter type.
  • The parameter is not being used in a query that supports dynamic binding (e.g., query folding is broken).
Essentially, Power BI is saying: “I see the binding, but I cannot guarantee it will work as expected.”

2. Why does the slicer not refresh the data?

Dynamic binding only works when:
  • The parameter is used in a native query that supports query folding.
  • The slicer column and parameter have matching data types (e.g., both text or both date).
  • The report is set to DirectQuery mode (dynamic binding does not work in Import mode).
  • The parameter is referenced in the query in a way that Power BI can rewrite dynamically.
If any of these conditions fail, the slicer will change visually but will not trigger a new query.

Quick Troubleshooting Tips

  1. Check Data Types
    • Ensure MonthYearForSlicer and p_SelectedMonthYear are the same type (e.g., text or date).
  2. Validate Query Folding
    • In Power Query, right-click the last step and check if “View Native Query” is enabled. If not, folding is broken, and dynamic binding will fail.
  3. Confirm DirectQuery
    • Dynamic binding only works in DirectQuery mode. If you are using Import, the slicer cannot trigger a new query.
  4. Rebind Parameter
    • In Model View, rebind the parameter to the slicer column and ensure the question mark disappears.

Why is this happening with large SQL sources?

Dynamic binding relies on query folding. If your SQL query is too complex or includes transformations that break folding, Power BI cannot rewrite the query dynamically.

 

If this response was helpful in any way, I’d gladly accept a 👍much like the joy of seeing a DAX measure work first time without needing another FILTER.

Please mark it as the correct solution. It helps other community members find their way faster (and saves them from another endless loop 🌀.

View solution in original post

4 REPLIES 4
v-ssriganesh
Community Support
Community Support

Hello @Aacuabo,

We hope you're doing well. Could you please confirm whether your issue has been resolved or if you're still facing challenges? Your update will be valuable to the community and may assist others with similar concerns.

Thank you.

v-ssriganesh
Community Support
Community Support

Hi @Aacuabo,

Thank you for posting your query in the Microsoft Fabric Community Forum, and thanks to @Zanqueta & @MFelix for sharing valuable insights.

 

Could you please confirm if your query has been resolved by the provided solutions? This would be helpful for other members who may encounter similar issues.

 

Thank you for being part of the Microsoft Fabric Community.

 

Zanqueta
Super User
Super User

Hi @Aacuabo

 

Dynamic query binding in Power BI can be tricky, especially when working with large SQL sources.

1. What does the question mark (?) icon mean?

The ? icon next to the bound column in Model View indicates that the binding is not fully validated. Common reasons:
  • The parameter is not correctly linked to the field.
  • The data type of the slicer column does not match the parameter type.
  • The parameter is not being used in a query that supports dynamic binding (e.g., query folding is broken).
Essentially, Power BI is saying: “I see the binding, but I cannot guarantee it will work as expected.”

2. Why does the slicer not refresh the data?

Dynamic binding only works when:
  • The parameter is used in a native query that supports query folding.
  • The slicer column and parameter have matching data types (e.g., both text or both date).
  • The report is set to DirectQuery mode (dynamic binding does not work in Import mode).
  • The parameter is referenced in the query in a way that Power BI can rewrite dynamically.
If any of these conditions fail, the slicer will change visually but will not trigger a new query.

Quick Troubleshooting Tips

  1. Check Data Types
    • Ensure MonthYearForSlicer and p_SelectedMonthYear are the same type (e.g., text or date).
  2. Validate Query Folding
    • In Power Query, right-click the last step and check if “View Native Query” is enabled. If not, folding is broken, and dynamic binding will fail.
  3. Confirm DirectQuery
    • Dynamic binding only works in DirectQuery mode. If you are using Import, the slicer cannot trigger a new query.
  4. Rebind Parameter
    • In Model View, rebind the parameter to the slicer column and ensure the question mark disappears.

Why is this happening with large SQL sources?

Dynamic binding relies on query folding. If your SQL query is too complex or includes transformations that break folding, Power BI cannot rewrite the query dynamically.

 

If this response was helpful in any way, I’d gladly accept a 👍much like the joy of seeing a DAX measure work first time without needing another FILTER.

Please mark it as the correct solution. It helps other community members find their way faster (and saves them from another endless loop 🌀.

MFelix
Super User
Super User

Hi @Aacuabo ,

 

The question mark (?) is the symbol that the specific field is a dynamic binding to the query you can see that on the documentation:

MFelix_0-1765900894168.png

What is the type of model you are using Import or DQ?

 

Be aware that for the dynamic binding to work the Fact table needs to be DQ and the dimension needs to be import or Dual model, creating a composite model.


Regards

Miguel Félix


Did I answer your question? Mark my post as a solution!

Proud to be a Super User!

Check out my blog: Power BI em Português





Helpful resources

Announcements
Power BI DataViz World Championships

Power BI Dataviz World Championships

The Power BI Data Visualization World Championships is back! It's time to submit your entry.

January Power BI Update Carousel

Power BI Monthly Update - January 2026

Check out the January 2026 Power BI update to learn about new features.

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.