I’m looking to utilize Glide as an order status page.
And whenever a specific order reaches a certain stage, We will send out an email with a URL to that specific order to our customer.
The URL in Glide is the row ID- yet because of the structure of how collections work in Glide, The URL will contain a breadcrumb to the previous page which is the collection containing all the orders. Which we don’t want to be visible to anyone.
We could add a filter for no one to actually see any of the items in the collection, but that will probably result in the direct URL not to work.
Any suggestions on how to create custom filters for public apps? since no user is logged in- so i can’t utilize the columns in the users table to filter values from my collection.
There are lots of ways to do custom filters, but yes you need to use User Specific columns. For non-signed in users, a simple approach is to sit your screen on top of a single row helper table, and then work from there.
I can’t comment on the SQL aspect of it, as I’ve not yet used any SQL data sources with Glide.
I would use URL parameters. Create a tab based off of a single row table. This tab can be hidden from navigation if needed.
The single row helper table has a template column to get the link to current screen (create a variable and replace it with link to current screen). Use a query column to query the order where rowID is included in template column’s deep link. Create a single value column to get the “whole row” from the query. From there you can use look up columns to bring in the data you need into the helper table.
The best part is that this table has zero basic columns which means it’s completely user specific.
The issue you’re trying to solve is allowing users to see their invoice without navigation to other invoices (by clicking “back” or “breadcrumbs”), yes?
If so, then, yes, it will need a slightly different setup than what I described above.
I’ve thought of pushing a variable via the URL Parameters but wasn’t aware that this feature already exists (I’ve wanted to use it in the past to prefill forms).
Your solution is beautifully clean and simple!
Will have it implemented shortly :))
