Hey @BenFortunato,
Once you’ve published the interface, you can take a look at it as an end user, apply all filters you’d like, and as you do so you’ll notice how the url on your browser gets updated.
It is not super clear at first sight how that url is constructed. However, if you copy such url and paste it on a new tab, the filters will be applied already.
Meaning: You can do the above to get pre-filtered pages/views as needed.
Limitation: If you actually need to build this views dinamically, you will have to spend some time understading how Airtable is building the url!
Hope this helps.
Feel free to reach out if you have any additional question.
Mike, Consultant @ Automatic Nation
The params are all base64 encoded and they basically give you the element ID, type of filter (is, is not, contains etc) as a number, and the value you’re trying to filter by (plaintext, select option ID, etc)
Unfortunately redirects with scripting aren’t possible though, so knowing this probably doesn’t help that much heh
What’s your workflow going to be exactly? Each button will open the products page with a different set of filters?
I started off this project in airtable not knowing much about coding and I think I’m outgrowing its limitations. I’m trying to wrap up what I have then shift to react and postgre site where I won’t have all these limitations.
I’m created a mini application using scripting flags (checkbox) and a user modification field to allow users to select records and then perform actions through a button. I also came up with a way for users to filter their view based on their project by creating a user preference table and adding a project record. In any project related field I then look up the user preference table and set the view filter to check if the current user = user from the project lookup.
Essentially I have instances where a user might want to access information on a junction table that is related to record or table they are currently using. With the airtable interface I would like to link to anouther table but then filter the table to the set of related records. Right now the user would essentially have to re-enter the data every time they move to anouther table, ie filter, yes I’m looking at product A variant B for example since there is no way to pass parameters or save state.
. . . and don’t get me started on lookups! My data schema is so bloated since you have to daisy chain lookup fields to get data from one table to the other. Great learning experience but time to graduate:)
