Is the parameter with text field control option case sensitive?
Hello @jjohnson, welcome to the Quick Community!
Yes, I believe the text field control is going to be case sensitive. It needs to be an exact match. That is why I don’t ever use it because it allows for too much user error.
Hi @jjohnson,
Just checking back in since this thread hasn’t received a response in a while. Were you able to see Dylan’s most recent response regarding your question? Please help the community by marking this answer as “Solution” or following up in general within the next 3 business days!
Thank you!
Any solutions where you can have search control that is not case sensitive or a work around?
Hi @jjohnson,
To workaround the case sensitive search, you can create a calculated field like the one below and put that into your visual:
With this, you will be able to search for the exact field you want as both words are being compared as lower-case. In my example below, it may still populate with nulls, but for that you can create a filter that only show values not equal to null.
Let me know if this would be able to work for your use case!
Thanks. I will give this a try and let you know.
How is the parameter ${PTextControl} setup and configured? My current parameter is grayed out and a message displays when I hover over it (Parameters without a default value aren’t usable in calculated field). I can’t have a value pre filtered for the data set I am displaying in a table as I need everything visible for the user to see before entering a text to search.
Hi @jjohnson,
I set the default as ALL_VALUES (as shown below), which makes it set to as the name suggests instead of a single value. This should enable you to utilize the parameter within the calculated field and for the text field control to work.
Hope this helps!
@WLS-Luis , hello. I am finally getting back around to this and I have my parameter setup with the default value of ALL_VALUES and that worked for me to create the calculated field. When I put the calculated field based on the below calculation into my visual, I get nothing but null’s. Now I am trying to create table/pivot table versus a chart like in your example so not sure If that has anything to do with my issue.
Hi @jjohnson,
Apologies for the delay in response. Is that still the case when you type something that matches one of the field’s potential values, or does it still populate as null? I just tried it in a table and I did get null by default, but after typing a respective value it populated as well. From there you can right click on the null value, and that should give you the option to exclude it from the table. If that is not the case, please let me know and I can look further to see why this could be occurring.
Thank you!
@WLS-Luis , I was able to get it to work for my table by setting up this calculated field.
ifelse(
isNull(${Search}), 1,
strlen(${Search}) = 0, 1,
isNull({description}), 0,
strlen(toLower({description})) > strlen(replace(toLower({description}), {safe_search_term}, '')), 1,
0
)
Now my text field control works whether or not I type north or North in the search bar.