Forum Discussion
How to pass Dynamic M Query Parameter into Slicer (Text)
Hi prabavathym,
Thank you for reaching out to the Microsoft fabric community forum. Also, thanks to srlabhe, for his inputs on this thread.
The behaviour you are seeing is expected because Dynamic M Query Parameters cannot be entered directly through the Edit Parameters dialog in a report. By design, they need to be bound to a field in your model so that end users can interact with them via a slicer or filter inside the dashboard. To make this work perfectly, do those steps in below mentioned.
Create a disconnected table with your possible parameter values. Bind your Dynamic M Query Parameter to that column. Add a slicer visual from that column, so users can pick the value directly in the report.
If you want true free-text entry (instead of pre-defined values), Power BI does not have a native “text slicer” now, in that case you can look at custom visuals like Smart Filter Pro from AppSource.
Refer this link for more information: https://learn.microsoft.com/en-in/power-bi/connect-data/desktop-dynamic-m-query-parameters
Hope this helps. If you have any doubts regarding this, please feel free to ask here. We will be happy to help.
Thank you for using the Microsoft Community Forum.
Thank for your reply.
I also tried this method : Create a disconnected table with possible parameter values. Binded the Dynamic M Query Parameter to that column. Added a slicer visual from that column, so users can pick the value directly in the report.
But client was looking for texting related visuals. Let me try with that custom visuals.
Hi prabavathym,
Thanks for getting back and sharing the additional details. You are right, Dynamic M Query Parameters work best when bound to a slicer or dropdown for user selection. At this point, there is not a built-in way to directly bind them to free-text inputs or “texting-style” visuals in Power BI.If the client specifically needs a text-entry experience, the best approach would indeed be to look into custom visuals that support text input. Another option is to provide a pre-populated lookup/disconnected table with possible values (as you already tried) and allow users to select from there, which is currently the supported method.
Hope this helps. If you have any doubts regarding this, please feel free to ask here. We will be happy to help.
Thank you for using the Microsoft Community Forum.Thanks for clarifying this. Makes sense that free-text entry isn’t supported natively with Dynamic M Query Parameters, and I’ll explore the custom visuals route for this requirement. Appreciate the suggestion about using a lookup/disconnected table as well—good to know the supported alternatives.
Hi prabavathym,
Glad to hear the clarification helped and that the alternatives make sense. Yes, currently free text entry is not supported directly with Dynamic M Query Parameters, so exploring custom visuals is a good next step.
If you decide to try that approach and run into any challenges with setup or functionality, feel free to share the details here we will be happy to help further.
Thanks again for updating the thread, and good luck with the custom visuals route.