# Problem with radio filters and query params stacking (AND instead of OR)

**URL:** <https://forum.finsweet.com/t/problem-with-radio-filters-and-query-params-stacking-and-instead-of-or/5487>\
**Category:** Attributes\
**Tags:** queryparam, attributes-v2, list-filter\
**Created:** [July 16, 2025, 6:33pm UTC](https://forum.finsweet.com/t/problem-with-radio-filters-and-query-params-stacking-and-instead-of-or/5487 "2025-07-16T18:33:26Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![coraline](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.finsweet.com/coraline/32/3658_2.png) [@coraline](https://forum.finsweet.com/u/coraline)\
**Post date:** [July 16, 2025, 6:33pm UTC](https://forum.finsweet.com/t/problem-with-radio-filters-and-query-params-stacking-and-instead-of-or/5487/1 "2025-07-16T18:33:26Z")

</div>

👋 Hi @Support-Luis @Support-Pedro

I’m having an issue with **Finsweet Filter V2**.

### Context:

- I have **2 filter lists** :  
➡ **Format**  
➡ **Client**
- Each list uses **radio buttons**.
- Both lists share the same **input `name` group** , because I want to allow only one filter selection at a time.

### The problem:

The filter works fine individually on either list.  
However, when I use Finsweet’s **query param** feature, I notice an unexpected behavior:  
👉 Instead of working as an **OR** (either one or the other), it behaves like an **AND**.  
So, if a parameter is already set in the URL, it stays active even when I select another filter.  
As a result, the filters are stacking up, whereas with radio buttons I want the previous value to be replaced.

### What I want:

When I select a radio in **Format** , it should replace any active filter from **Client** , and vice versa. In short: **only one active value at a time**.

### My question:

➡ Has anyone already faced this issue?  
➡ Is there any specific setup required with Finsweet radios to avoid this “AND” behavior via query params?

Thanks a lot in advance for your help! 🙏

[RO](https://preview.webflow.com/preview/dafonseca-production?utm_medium=preview_link&utm_source=designer&utm_content=dafonseca-production&preview=674238265a99974405650b0623c09de3&pageId=67f29e6522455a5d04df148e&locale=en&workflow=preview)

---

<div class="post-metadata">

**Author:** ![coraline](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.finsweet.com/coraline/32/3658_2.png) [@coraline](https://forum.finsweet.com/u/coraline)\
**Post date:** [July 18, 2025, 1:34pm UTC](https://forum.finsweet.com/t/problem-with-radio-filters-and-query-params-stacking-and-instead-of-or/5487/4 "2025-07-18T13:34:22Z")

</div>

With custom code, filtering eventually works! But… it seems incompatible with the active state… and I need to have an active state for users to find their way around.

Can you help me?

---

<div class="post-metadata">

**Author:** ![Support-Luis](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.finsweet.com/support-luis/32/53_2.png) [@Support-Luis](https://forum.finsweet.com/u/Support-Luis)\
**Post date:** [July 18, 2025, 10:45pm UTC](https://forum.finsweet.com/t/problem-with-radio-filters-and-query-params-stacking-and-instead-of-or/5487/5 "2025-07-18T22:45:34Z")

</div>

Hey @coraline! I’m taking a look at what the best approach here is. I’ll let you know as soon as I have something we can work with!