Filters not working in complex Nest and Combine set up

Attributes
, , , ,
1

I am combining 3+ lists and nesting filters (not working)

Using Load + Combine + Nest + Filters (mix of V1 + V2 with legacy solution already in place)

I am building a resource library that will bring together several CMS collections - currently working with 3 but expect it to grow to 5 or more. The 3 lists I have set up are combining correctly.

I am also nesting filters into each list as I can’t have more than 2 nested collections. These are also pulling into the card as expected.

In the past I have had no trouble implementing Filters with fs attributes but I can’t seem to get it to work on this occasion.

2

Hey @andrew1!

Looking at your current setup with the mixed v1 and v2 attributes in your Load + Combine + Nest + Filters implementation, I can see what’s causing the issue.

When you mix v1 and v2 solutions on the same page, they don’t work together reliably. The main problems come from instance conflicts and how these different versions interpret each other’s elements.

We recommend migrating fully to v2 for these reasons:

  • v1 is discontinued and won’t receive updates
  • v2 handles complex multi-solution scenarios better
  • v2’s instance system prevents the conflicts you’re experiencing

You can have both versions on the same project, but what you cannot do is mix both versions on a single page.

Try implementing this approach and let us know how it goes!