I would like to have a search bar (address) on the main page of the website + a search bar in a header, both returning results on the same page that I called (search results).
I initially created a “thing” called search but then I realized it would save of the search of the servers…
So, what is the best way to return results on a separate page?
My understanding is you have a search bar with a “Search” button in different locations and when you click the button you want to open a page that displays the search results.
When you click the button, you’d send the text the user typed in the Search bar to the “Search results” page and have a Repeating Group there that displays the results.
You can open this page from any other page, header etc.
If you go to the dashboard you’ll find a super useful lesson: “Sending data to pages” that will show you how to do this. Let us know if that doesn’t suffice!
Create a thing of type text called search query.
Send it to the search results page and use it to perform the query using a repeatable group there.
You can and most likely should have it on the user object.
I tried to create a Thing called “query” and send it to the “search result” page. I think it worked But it means that each query will be saved onto the database, right? I would like to avoid this.
I would like to just use the address typed by the user on the main page and display the results in a repeating group on another page (“search Results” page). Exactly like you can do when the search bar is on the same page as the repeating group displaying the results.
Storing searches cab be a very useful site use metric as you app matures, to understand users and their search patterns.
If you absolutely do not want to store that information for privacy reasons you can always delete it when the user moves away from the search page - there’s an action for that