Welcome to the Alloy Ideas Portal đź‘‹ Here, you'll be able to browse improvement ideas raised by our community, vote on ideas you agree with or even raise your own ideas. We review all ideas raised and we endeavour to respond to all raised ideas.
Any ideas submitted will be immediately visible on the portal for others to vote on, please do not include anything in your ideas you do not wish to be shared with others.
As part of the search settings, I believe it would be useful to have a secondary search type. Where, if the initial search fails to find any results, the search would then take place using the secondary search type.
For example, my preference to search the NLPG premises design is "starts with". Which generally works well to find the exact address I'm looking for e.g. "27 High Street" without seeing the hundreds of properties in the street. However if it is a named building e.g. "1 Urban Court High Street" and I'm unsure of the naming convention. It would be convenient if I could search the name of the building "Urban Court", without changing my search settings, and it would find the item using the secondary search type of "word match" or "all attributes".
Hi Joshua,
thanks for raising this with us. I thinkk this use case can be covered by using a parameterised saved query. These are really useful and would allow to pop have a query over the NLPG design, and have a text field pop up for the text you wish to search for. This will then allow your AQS query to be built to say find my premise where the title starts with "my text" or the title contains "my text".
There is an example of how to do this on our help page - https://help.alloyapp.io/web/aqs/aqs-builder/aqs-example-4, have a look and let me know how you get on.
Thanks,
Andy
Thanks for the suggestion Andy, I am familiar with saved queries and parameters but they are not my most favoured way to search, when looking for things quickly at least, there are too many clicks with saved queries and not they are not ideal for multiple searches in succession. I do use AQS for more advance queries or for our users who want a "foolproof" way of finding what they are looking for. Hopefully it can still be considered as a future improvement to the search function. Thanks, Josh : )