Interface Filter Element URL

It would help if someone could shed a light on this works and can be used.

Thanks @Shayan_Zadeh, and yes please. I’m still looking and waiting for a solution. And since the recent interfaces update, there’s slightly less functionality with filter elements. I think these need some attention to ensure interfaces are a winning product!

I have the same problem here. Trying to figure out the url patterns for filters in order to build custom page links

Same here 😞

Pretty please add these IDs as a function of the RECORDID() in formulas

STILL waiting to understand this.

Is it still not possible to do this?

This feature would be awfully useful! I often would need to program custom urls to interface pages by taking in account filter elements values.

Still no answer after over a year on a feature that is ALREADY BUILT. Literally all we need is some documentation, or resource on where the developers are pulling that id from. So disappointing.

I believe [Interface] Use Data to Populate Connected Filter ... - Airtable Community   is a new idea request for this to be implemented. 

Hey, 

i had the same issue and just tried a few things.

The parameter for setting the filter is

b followed by a URL encoded colon (%3A) followed by a Base 64 encoded record that looks like this in my case:

{"lmq2i":[[6,["rec5N7fBUoLjX5wh8"]]]}

In your case (eyJBYk5NTyI6W1swLFsicmVjWEtBdGMzQmJaY0JlaUYiXV1dfQ) it contains this:

{"AbNMO":[[0,["recXKAtc3BbZcBeiF"]]]}

The first element seems to identify the filter (AbNMO), don't know what the integer value indicates but then follows the record ID for the elements selected in the filter.

Hope this helps. 😃

It worked!! THANK YOU! First decoded the url after the %3A as described. Then used the script shared here to encode it with the desired recordID filled in. Thank you!!!

Could you give more details about how you did this? Are you using an Automation Script step to create the link to the interface for the record at record creation? Could you share your script if so?

I think I've managed to solve this:
I tested it on a "blank page" interface, it has a filter element and a grid table

When I select one element in the filter element (linked records), the URL looks like this:

https://airtable.com/{{base_id}}/{{interface_id}}?2HzwN=b%3AeyI4dGtRNiI6W1s2LFsicmVjbFpqMzhmMVhwcERUMXEiXV1dfQ   

normally, when using a record picker, the querystring looks like this: ?2HzwN={{record_id}}

Turns out, that the long string starting with "b%3Aey..." is base64 and url encoded, you can decode it using GPT4 quickly, which will give you the output of:

{"8tkQ6":[[6,["{{record_id}}"]]]}

Knowing this, you can generate the dynamic link using make.com for example. It's going to look like this:

https://airtable.com/{{base_id}}/{{interface_id}}?2HzwN=encodeURL(base64 ("{""8tkQ6"": [[6, [""{{record_id}}""]]]}"))

Tested this out manually on a couple of examples and it seems to be working, the output is a working url to the interface, which after clicking, opens the interface with a prefilled filter element

EDIT: I've just only now seen u/einfachiso's reply (it wasn't pinned on the first page :D). The solution seems to be the same

 Great Work! Thanks for sharing in detail. It would be nice to see Airtable help out here and make this a bit easier 🙏

Very smart solution and thanks for sharing.

That said, shame on Airtable!  Navigating between Interfaces with some session data that dictates filters and other parameters is a core and common aspect of any application.  The fact that their architecture actually does support this, but that they haven't provided an INTERNAL (not requiring Make) way of executing this is baffling! 

Common use case - Interface to views a list of Clients.  After selecting a specific Client, and the Interface showing their information, I want to navigate to a different Interface that pulls up an assessment on that client (so navigate to the page and preload the filter the the correct client's assessment).  Very common!

Before these LCNC platforms can truly start to displace bespoke applications - these types of common functions must be present.

Thanks for your answers! I implemented the link logic and was able to get the link with correct filter with script. In my case, there is still a missing point: 

I got a single interface for all clients (gallery view and record review), then put a filter dropdown and shared it as public. From the public link, I selected a client Contact from the dropdown filter and the URL for this selection has a particular pattern which I managed to reverse engineer and replicate for other clients using a script automation. So, I got an already filtered URL for each client and added it as a field in the base with  automation.

Now, the missing point is that the filter is still there, and a filtered client can still see other clients from the dropdown. I tried to remove the filter item from the interface design but after publishing it, the filtered URLs to interfaces no longer worked (went to an unfiltered view by default, after bringing the dropdown back the same URL worked well again). While I was trying earlier, I had one experiment where I found that even after removing the filter element from design, I was getting the filtered view for client which is exactly what I needed (giving a personal URL to each client without seeing other clients). I'm not sure if this successful experiment was an bug or an illusion in my case because I wasn't able replicate it afterwards. 

Please let me know if you know any solution for this case or any workarounds. Thanks! 

I think the only option would be to set up a dynamic filter for Client's email contains Current user email, but I don't think that can be done on public interfaces? Your clients would need to log in to Airtable I guess.

To do that, you'd need to set up a column of Type Email in the Clients table (it can also contain multiple emails separated with commas) for the dynamic filter to work.