How to pass Dynamic M Query Parameter into Slicer (Text)

[prabavathym]

Hi all,

I’m working with Dynamic M Query Parameters in Power BI. I’ve created a parameter called Product (screenshot attached). The setup works fine, and I’m able to see the Edit Parameters dialog.

Now, I want to bind this parameter to a text slicer so that users can type a value it the slicer, and it should pass that value into my parameter.

I’ve already:

Created the parameter in Power Query

Configured it as a Dynamic M Query Parameter

Bound it to an empty column

i would like to pass this as text slicer.

                                     i would like to pass this as text slicer.

Is there any way in which we are able to pass this value inside our dashboard using slicer. Because everytime we will not able to open transform data - edit parameter- then changing the value and click ok(I dont think this as an efficient way).This method will lead an issue in powerbi service also. 

So i want smthing inside my dashboard similar to text slicer. I need to pass the value using that text slicer. 

Has anyone implemented this before?
Thanks in advance

[v-kpoloju-msft]

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.

[prabavathym]

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.

[v-kpoloju-msft]

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.

[prabavathym]

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.

[v-kpoloju-msft]

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.

[prabavathym]

Thank you

[v-kpoloju-msft]

Hi @prabavathym,

Just checking in to see if the issue has been resolved on your end. If the earlier suggestions helped, that’s great to hear! And if you’re still facing challenges, feel free to share more details happy to assist further.

Thank you.

[v-kpoloju-msft]

Hi @prabavathym,

Hope you had a chance to try out the solution shared earlier. Let us know if anything needs further clarification or if there's an update from your side always here to help.

Thank you.

[v-kpoloju-msft]

Hi @prabavathym,

Just wanted to follow up one last time. If the shared guidance worked for you, that’s wonderful hopefully it also helps others looking for similar answers. If there’s anything else you'd like to explore or clarify, don’t hesitate to reach out.

Thank you.

[prabavathym]

Thank you again for checking in and for your kind support . I tried the suggested solution, and I also explored using custom visuals — but unfortunately, I’m still not able to make the parameter typable in Power BI. Right now it only works as a dropdown or predefined list.

Thanks once again for your patience and guidance.

[v-kpoloju-msft]

Hi @prabavathym,
Thank you for your update, and I really appreciate your patience while testing the suggestions.

Currently, in Power BI, parameters are limited to dropdown or predefined lists free text/typable parameter input is not supported natively. This is why you are only able to select values but not type them directly. As possible workarounds, you might consider.

Using a What-If parameter combined with a slicer this gives predefined ranges but still allows some flexibility.

Creating a disconnected table that users can interact with (e.g., entering values via Excel or SharePoint list) and then binding that input to your model logic.

Also, kindly refer these links:
1. https://learn.microsoft.com/en-in/power-bi/transform-model/desktop-what-if 
2. https://learn.microsoft.com/en-us/power-bi/connect-data/service-parameters#considerations-and-limita... 

Also, please refer this solved thread which is helpful to you:
https://community.fabric.microsoft.com/t5/Service/List-parameters-m-query-not-shown-as-drop-down-in-... 

If free-text input is critical to your scenario, I would recommend submitting an idea or upvoting similar ones on the Power BI Ideas forum Fabric Ideas - Microsoft Fabric Community
So This way the product team can consider adding it as a feature in the future.

Hope this clears it up. Let us know if you have any doubts regarding this. We will be happy to help.

Thank you for using the Microsoft Fabric Community Forum.

[v-kpoloju-msft]

Hi @prabavathym,

Just checking in to see if the issue has been resolved on your end. If the earlier suggestions helped, that’s great to hear! And if you’re still facing challenges, feel free to share more details happy to assist further.

Thank you.

[srlabhe]

Just try to use the Parameter in slicer, isn't that simple?

[prabavathym]

No it doesn't pass into text slicer. If i pass this into an dropdown slicer also it will be empty as it dont have values in it, (its not normal parameter, its dynamic m query parameter)

[srlabhe]

Use the field in slicer where you binded your parameter to 

[prabavathym]

Thanks for the suggestion!

I did try using the field that I bound my Dynamic M Query Parameter to in a slicer, but since it’s just an empty column, it doesn’t provide any values to work with. What I’m really looking for is a way for the end-user to manually type or enter a value in the report (like a text input box), and then have that value passed directly into the parameter at query time.

From what I understand, normal slicers only work with predefined values in the model, but in this case I’d like it to work dynamically without having to populate the column with static values.

Has anyone managed to simulate this kind of “text input slicer” for Dynamic M Query Parameters? Or is there a workaround ?