Hi! I’m having some issues using CMS Nest and CMS Filter. I’ve used nest to bring into my collection item some multi-reference field from the cms collection. I’m being able to filter by the search imput, but when I try using tags to filter as well it’s not working.
Here’s my read only link. Thanks!
Hey @juanignacio.vilaplan! I noticed you are using V1, I highly recommend you updat the setup to the V2 version.
You can find all available solutions here →
Hi Luis, thanks for your response!
I’m still experiencing the same issue. I replaced v1 with v2 and followed all the steps as instructed.
As you can see, the groupers on the left use the same CMS collection, but are filtered to act as tags for the filters. The thing is, these tags refer to a multi-reference field on the item being filtered in the list, and that field is connected using CMS Nest.
My question is: how can I get this to work?
Hope I was clear enough—thanks in advance for your help!
Here’s the read only link for this v2 test!
Hey @juanignacio.vilaplan! You are only missing one step!
You’ll need to add the fs-list-field = IDENTIFIER to the collection items on the template page.
It should look something like this!
Let me know if this solves the issue!
Hey @Support-Luis ! Still not working.
Do I need to paste the script code in the cms page as well?
However, I found that attributes v2 still does not support filtering by nested collection values (inside a multi-reference field). That’s because filters in Attributes v2 only read static or directly available CMS-bound fields — they cannot look “inside” CMS Nest components.
Is that correct?
Thanks!
