New Finsweet Filter Attributes2 Help

Design help CMS
1

I’m working on a blog page for a client. What I’m trying to do seems simple enough: I have a blog, want a filter by category. Some posts have multiple categories so I have a multi-reference field in the blog post collection. When you select a category from the dropdown, the Empty State appears. I definitely have something wrong with the connection between the filter items and the post content.

Here is my public share link

2

Hi there,

Collection lists can be filtered using various field types. For filtering with multi-reference fields (such as categories), you can:

  • Use the Collection List filter settings to match specific categories
  • Set up multiple conditions to filter by different category combinations
  • Create dynamic filtering by connecting the filter to CMS fields or URL parameters

To set this up, go to your Collection List settings, click the filter icon, and select your multi-reference field. You can then choose the matching criteria and select the specific categories you want to filter by.

For more complex filtering needs, you can also combine multiple filters or use custom code solutions.

Hopefully this helps! If you still need assistance, please reply here so somebody from the community can help.

3

Hi Alyssa, make sure to read the docs.
v2 has more control, so you actually specify the filter value you’re using rather than have it inferred from text content.

4

Thanks for the note! I’ve actually watched the documentation several times (haha). The issue ended up being pretty specific: because I’m using a multi-reference field, the checkbox needed a manually added value attribute that matches the linked category name. All good now — thanks!

Screenshot 2025-05-27 at 4.39.27 PM
Screenshot 2025-05-27 at 4.39.27 PM456×278 6.88 KB

5

Back at my desk- that’s exactly the one was referring to. :grinning_face:
I like that level of control.

There’s another change to watch out for which relates to fs-list-instance.
The concept of list-as-datasource has standardized and generalized so e.g. the List Select attribute and List Filter attribute both use fs-list-element = list to identify their content sources.

That means you have to segregate them with fs-list-instance to avoid attribute collision.

You can use arbitrary text strings as an identifier, so I’m using e.g. fs-list-instance = color, fs-list-instance = products, and so on. Very tidy. Just you know, be careful about moving elements in the nav, there’s nothing protecting these element-container arrangements, but they are essential for the scripts to work.