Connect with peers, share your expertise, and inspire what’s next in Smartsheet — from proven practices to practical how-to insights from fellow users and product experts.
Sign in to join the conversation:
Hi all,
Our current LOOKUP and MATCH functions are case sensitive, e.g., "my task" will not match against "My task".
Would folks expect these functions to be case sensitive, case insensitive, or do you have no preference?
Thanks,
Daniel
I would say that changing capitalization is a common mistake and horrible way to intentionally differentiate entries, so I would expect searching functions to ignore it by default.
The best solution would be a "Match Case" checkbox or separate case sensitive and non-case sensitive functions (like Find vs Search in excel)
I concur with Eric. Though I know that some functions in Excel and Google Sheets are also looking for case sensitivity, it would be cool to have an optional modifier in the function to choose to be case-sensitive or not. Sometimes this modifier is found by including a 1 or 0 after the function, as an additional parameter of the function. I would expect that smartsheet would set up the function similar to what other users are used to but adding an optional criterion to turn on, or off, the case sensitivity could be useful.
Thank you both, we are looking into changing LOOKUP and MATCH to be case insensitive, to help users avoid unintentional errors due to case mismatch.
If you can think of a particular scenario where you would want to be able to toggle these to case sensitive, please let me know.
I would like to have the option to make it case sensitive or not. (Sidenote: I use the FIND function, and that is also case sensitive, even thought I don't always want it to be)
We will change the VLOOKUP and MATCH search term to be case insensitive in the coming month. In addition, the "true/false" parameter in VLOOKUP will no longer be case sensitive, so you can type "True" or "TRUE." You will also be able to enter 1 or 0 instead of "true" or "false."
These enhancements should help to avoid errors while typing formulas. Some existing errors may go away when we release.
I also use FIND, would like if that function is not case sensitive. Is there any way this may also happen?
Thank you,
Cel
Adding an optional parameter to control this would have been so much better
Hi all, I am trying to build out a formula that will return "True" if the CIF #@row can be found above it in the same column (CIF #) AND the Days Since Created is between 30 - 365 days. All of the formulas I have tried have only gotten me so far as the "AND". Adding in the dates screws it up. The goal is to determine if…
I am getting a lot of REF errors for my predecessors and I can't figure out why. At first I thought I might have REF for predecessors to predecessors but that's not the case. When I export the file into Excel it shows the IDs in the place where it shows REF in SS. Each time I refresh the file I feel like different values…
I am trying to create a sheet summary, where the field is a formula that relies on a contact card within a column. However, it keeps returning a result of "#NO MATCH". The columns involved are, 1:) Priority (symbol column) for Up, Unchanged, and Down, and 2:) Contact Card column. I am trying to get a sheet summary formula…
