Forum Discussion
Helper IIIGet the user input stored in a parameter
I have a requirement where I have to give a search bar like visual and the end user will give an value. The value entered by the user should be captured and it should be used to filter the visual.
I'm not sure how to do that. Recently, I read an article about dynamic m query but in that all the values should be there in a table which will be binded.
In this case, user can enter anything.
Is there a way to capture the user input in a parameter?
or is there a custom visual which captures the value entered by the user?
Any other thoughts on this?
Hi, Imagauthamam
You can try the following methods.
Slicer table:Measure:
Search = SEARCH(SELECTEDVALUE('Slicer table'[Slicer]),Max('Table'[Description]),1,BLANK())Count = Var _table=SUMMARIZE('Table','Table'[Date],'Table'[Ticket Number],"Count",[Search]) Return COUNTX(_table,[Count])+0Is this the result you expect?
Best Regards,
Community Support Team _Charlotte
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
4 Replies
jtspilkerHelper I
Imagauthamam struggling to understand how a freeform entry would be able to filter data without hiccups if a user mis-types something or doesn't enter an applicable piece of information.
did you know the default slicer has a search function built in? Create a slicer that houses the field users would search on and would filter your data. Guessing there could be lots of data people can search, so a dropdown list is probably best. Then, on the slicer itself on the report page, click the 3 dots and select the Search function. User can now click the dropdown, and the first thing they see is the ability to type something into the search bar, and any records that match part or all of what they searched will remain for them to select
ImagauthamamThanks for the response. But my requirement is different. Let's say I have a ticketing data. It has columns like ticket number, date and description.
The above attached image is the input data. Let's suppose the user enters "Access" in the prompt it should group the data by day level and give the count of how many times that word is present in description column.
- jtspilker
ah interesting. one idea: is there anyway you can add a column to the underlying ticketing data that basically is an "Issue Type" that assigns a high level category to each ticket (like Access, Login, Password, etc). you can then have a COUNTROWS measure on your ticketing data table, with a slicer that allows users to select which issue type they want to see.