I’m trying to see if it’s possible to make the following work:
A dropdown that selects a style which filters the sizes available, then the dropdown of the sizes (filtered) filters the info on the screen. See design screen grab.
Separately, to see if it’s possible to combo filter (see inventory screen) where there is a series and a style that are both contained in the fs-list-field = model and using an fs-list-operator = contain to filter the same field or if it works by using a duplicate field with a different field name but with the same CMS data. See link.
We can see what you’re trying to achieve — these are two distinct filtering scenarios that go beyond standard attribute setup.
What DOES work natively with fs-list:
The fs-list-operator="contain" operator exists and works great for filtering
Multiple filters can work together using matching logic attributes like fs-list-filtermatch="and" or fs-list-conditionsmatch="or"
You can definitely filter by multiple independent fields (series, style, size) simultaneously
Where things get more complex:
1. Cascading/dependent dropdowns (your SERIES→SIZE scenario where selecting a series filters available sizes):
This type of dynamic behavior — where one dropdown’s options update based on another dropdown’s selection — isn’t something fs-list handles natively through attributes alone. This would require custom JavaScript using the fs-list API for programmatic filter control.
2. Combo filtering same field with contain (multiple filters targeting the same CMS field):
We’re not finding documentation that confirms multiple filters can target the same field with the contain operator simultaneously. The duplicate field approach you mentioned (creating two separate CMS fields with the same data but different field names) may actually be the most reliable workaround, but we’d need to verify the specifics with our team.
Before we dive deeper, we need to clarify your exact requirement:
For your SERIES→SIZE scenario: Do you need true cascading behavior where selecting a series actually changes which SIZE options appear in the dropdown? Or would it work if both dropdowns function independently, and selecting both just narrows the results shown (without changing the dropdown options themselves)?
This distinction is critical — if independent multi-field filtering meets your needs, that’s straightforward with native attributes. If you truly need cascading (dynamic option updates), that’s a custom JavaScript implementation.
Series>Size: Ideally it would filter the options as not all sizes exist for all series. However, a fallback option could be to have all sizes available and when selected display N/A for price. But if I were going to do that, I would more easily switch to a tab structure and tab the series and filter sizes by series for each tab.
Combo filtering. Duplicate fields with different names is fine. Does fs-list-filtermatch=”and” apply here? I want each filter checkbox group to be expansive/OR logic. If I add two series it should display both. The 2nd filter checkbox group for Series should be AND logic to the first group and with all other filter groups (which I believe is already native behavior) but OR logic within it to ALL my filter groups if I want each additional filter to narrow down my choices? Would this still allow OR logic within a filter group.
I seem to have the combo filter set up correctly with duplicate renamed fields (same CMS data but different field labels), however only one of them works at a time (seems to be the first one used). Model & Series.
Additionally, the documentation seems to be wrong. When not explicitly set to fs-list-operator=”contain” the filter doesn’t work unless the value is an exact match. In the documentation it says contain should be the default.
What I need ideally is somebody to look at my read only and explain why the combo filtering isn’t working with 2 different field names using contain logic. Only one will work at a time for Series and Model. But can’t figure out why. It should work?
Combo filtering. Duplicate fields with different names is fine. Does fs-list-filtermatch=”and” apply here? I want each filter checkbox group to be expansive/OR logic. If I add two series it should display both. The 2nd filter checkbox group for Series should be AND logic to the first group and with all other filter groups (which I believe is already native behavior) but OR logic within it to ALL my filter groups if I want each additional filter to narrow down my choices? Would this still allow OR logic within a filter group.
