Does anyone know know how to make a filter option say “contains current location” when linking to a reference field in airtable? In one CMS template page design it has a filter on a collection set to [Locations “contains” current location"] but in another CMS template page which is referencing the same airtable and same field, I can’t set the option to “contains current location” - it only gives the option of setting it to “contains” and a single selected location…ie - it won’t make it so it is set to dynamically change based on the page’s dynamic location as pulled from the CMS collection in airtable.
Does anyone know why this would be or could help with this?
What I’m trying to achieve is that the filter only shows records that “contain” functional medicine and “contain” the page location name. The CMS template page I’m wanting this for is called “functional medicine” and it is creating functional medicine pages based on location:…ie - so that the url will be /functional-medicine/perth or /functional-medicine/brisbane etc. In airtable for this CMS each record name is a location and I want it to display only practitioners who have “functional medicine” as a specialty AND only those in the location of the name of the page. The filter is linked to our practitioners table in airtable which has the “locations” field and also has their “specialties” field.
So…a working example: There are records in this Functional-medicine airtable template that will dynamically pull through the name (being the page name location)…say it is Perth. So then on the filter on this page i only want it to show practitioners that have a specialty of functional medicine (that filter I can do) AND those that are in the current page location ie - in Perth…but it won’t get me a “contains current location” option, it will only give me the option to select individual location names but I want that to be pulled from the page name from the CMS item.
If those are the right practitioners to show then you’d design your Practitioners section with the collection list bound directly to that multi-ref field, rather than the Practitioners collection.
Alternatively, if you want a more searchable page, like “Find all practitioners who practice X in city Y”, you’d want to to build a filter page. I prefer Finsweet CMS filter for that.
Hi - thanks so much…however the actual collection within that functional-medicine page is actually linking and pulling through data from the “practitioners” airtable table…not that field you have shown there.
This is the same set up as the “locations” page…that pulls data through from the “practitioners” airtable tab. On the Locations template page there is a “contains current location” option in the settings (see screenshot) but there isn’t this option on the functional-medicine page above.
In essence - this is really my question - why does it have this option on the “locations template page” in the filter settings whereas it doesn’t have this option on the “functional-medicine page” even though both collection lists in these pages are set up the exact same way - ie - they are both set up linking to the ‘practitioners airtable tab’.
Here is another share link…hopefully you’re able to see the “locations” template CMS page?
And also…sorry I should have commented that as per your point above with the practitioners field as the multi reference and that as you say: "If you look at the Functional-medicines collection, the way you have the data structured is that the practitioners are stored in a multi-ref field.
I’m assuming those are the practitioners who practice Functional Medicine in that city, e.g. here in Hobart…"
That is the logic I wanted to set up for that field in airtable for that column that it would only show practitioners who are functional-medicine in hobart and then next row ‘functional medicine practitioners in sydney’ etc according to the right location but i couldn’t get the field to have 2 filters in it. Or in other words 2 parameters in it. Those practitioners listed are just all practitioners in hobart (not just the ones that are functional medicine and in hobart) for example.
If you know a way of applying those 2 logics to that multireference field in airtable then absolutely yes I would change the collection list in the template page to be linked to that field in my airtable for functional-medicine and not be linked to the ‘practitioners’ airtable.
I don’t have much advice for the Airtable side of things as I haven’t tried adding complex field-level filters or validation rules to my setups.
i’d really have to dig into your goals and data architecture to be certain, but if you’re wanting Webflow to publish a page dedicated to “Functional Medicine in Hobart” with a list of providers specific to Functional Medicine and Hobart, you really only have two directions…
Custom code to pull that data together and display it. Finsweet CMS Filter + CMS Load can be used for this, “hidden” on the page, but it’s not ideal for SEO.
Xref pattern, where you manage those relations in a separate collection.
Let’s talk about #2.
You’d have something like…
Locations - e.g. Hobart
Specialties - e.g. Functional Medicine
Then your cross-reference table;
Specialty Locations - e.g. Functional Medicine in Hobart
It would contain a single ref to Location and to Specialty, and then a Multi-Ref to the Providers.
This way you can easily generate a page that’s specific to Functional Medicine in Hobart, and list the Providers ( Clinics too if you want ).
I’ve written a bit about that here-
The tradeoff is admin, you have to manage that data in a separate table. Since you’re using Airtable, there -might- be a way to define and sync Views from Airtable to WF, which would let you admin e.g. Locations and Specialties on the Provider record directly? And then have those relationships split into your separate xref table in Webflow to support your collection page requirements. Maybe.
The key challenge here is that you have a highly relational schema for your data structure, and the Webflow CMS is not relational, it’s a document store. That makes it impossible to query and create views as a layer of abstraction, to feed your collection page setup. The data has to be structured directly to create those pages.
I always start from the views / SEO I want first, and then work backwards to define the CMS schema that will support that.
I think I’m tracking.