Wildcard character "*" in Power Search
Y
YES Integrations
Problem:
When using power search with part of a word matches for the whole word will not be found.
This can be particularly irritating when using power search an abbreviated serial code or other unique identifier - the abbreviated code is often still unique in SmartSuite records, but Power Search will not find it.
Solution:
Allow use of a wildcard character "*" to fill in unknown parts of searches. This will bring Power Search in line with other search tools like OS file system searches and web search engines.
Jon Darbyshire
Thank you for posting, YES Integrations! I have a few more questions for you:
- Can you provide examples of specific searches where the lack of a wildcard character has hindered your search results?
- Are there any specific areas within the Power Search where you feel the wildcard character would be most beneficial?
- Do you foresee any potential issues or complications that could arise from the implementation of a wildcard character in the Power Search?
Y
YES Integrations
Jon Darbyshire
- We store codes for government schemes on smartsuite. These codes ofter start in a large number of zeros. Often only the non zero part of the code is relayed in communications. Power Search is unable to find the correct record using only the non zero part of the code
- Finding partial matches when you have incomplete data
- It will be harder to search for text that already includes the "*" character. You probably also want to implement forced exact match searching using quotes