Filter tags joining together & duplicating in V2?

Attributes
,
1

Hey gang, cannot figure out how to separate filter tags to be individual like they were in V1. Not only do they join together if they’re in the same dropdown, but then a new filter tag with replicates that + any other new filters from other dropdowns.

I’ve seen some earlier posts that suggested a custom code solution from a month ago - checking if there’s any other more robust solution since then? :folded_hands:

Site URL

image
image1766×358 25.7 KB

2

Hey @julie! :waving_hand:

We can see exactly what’s happening with your filter tags in v2. This is a common issue when migrating from v1 to v2.

The issue is that Finsweet Attributes v2 handles multi-select values differently than v1. When you select multiple values from the same dropdown (or multiple checkboxes in the same group), v2 combines them into a single tag by default, whereas v1 would show each value as a separate tag.

Looking at your HTML structure, we can see multiple filter elements with the same data-name attributes, which confirms you’re using multi-select filters.

Here’s how to fix it:

The most robust solution is to ensure your filter structure is properly set up:

  • Verify your tag template has a div with fs-list-element="tag" containing text elements for the field name and value, plus a remove button
  • Make sure each checkbox/radio has the correct field name and value attributes.
  • Check that all checkboxes/radio buttons in the same group share the same Name attribute in Webflow. This name should not be shared with other unrelated form elements.

Let us know if you need additional help! @Support-Luis or @Support-Pedro can assist with any custom code solutions if needed.

3

Thanks, but I’m still stuck in the same spot because I believe my setup is as per what you had suggested. @Support-Luis @Support-Pedro All my checkboxes in the filters have the right name & value attributes & the tags are set up properly - I didn’t understand what “containing text elements for the field name and value” meant.
Here’s a loom of my set up: Troubleshooting CMS Filters and Tags Setup 🔧 | Loom

See the last image - for each filter I add it is adding it as an “AND” requirement to the previous (different) filter

image
image2578×526 81.2 KB

image
image2512×540 134 KB

image
image1790×414 27 KB

4

Hey @julie! This is the name field we are referring to, the “Name” under the checkbox settings.

A good practice is to name the checkbox with the same value used in the fs-list-field attribute.

Screenshot 2025-07-04 at 19.10.42
Screenshot 2025-07-04 at 19.10.421920×1094 134 KB

Showing our Filter example below.

Screenshot 2025-07-04 at 19.13.57
Screenshot 2025-07-04 at 19.13.571920×1097 172 KB

5

Thanks @Support-Luis that solved the issue for across filters! I’m still getting names in the same tag if it’s from the same filter. From the filter example, that’s how it’s also showing for the multiselect option (where Make tag has both Glimmer & Nimbus in it)

image
image1738×434 34.3 KB

How can I make everything an individual tag like they were in V1 from the same filter?

6

Hi @Support-Luis @Support_Rohan any suggestions for this? Trying to push live this week :smiley: Thanks so much!

7

Hey @julie! I’m afraid that this is by design and a different approach from v1. So, having a single tag for each filter field is not possible natively.

However, there was a workaround shared here in case you’d like to have a look

8

thanks @Support-Luis but that’s a bummer :frowning: I’m not super technical so that doesn’t look feasible. Would mention this in Finsweet docs that single item tagging is not in V2, I would have assumed it’s same V1 baseline + new features.

UX-wise I really can’t think of use cases where by design single item-tagging would not be applicable, curious on the thought process there

9

Thank you, @julie, for your feedback!

I will share with the team and see what we can do.

If you consider implementing the solution shared by @Linesy please let me know!