# The CMS list select field is disappear after use one times

**URL:** <https://forum.finsweet.com/t/the-cms-list-select-field-is-disappear-after-use-one-times/4842>\
**Category:** Attributes\
**Tags:** cmsfilter, cmsselect\
**Created:** [May 19, 2025, 9:54am UTC](https://forum.finsweet.com/t/the-cms-list-select-field-is-disappear-after-use-one-times/4842 "2025-05-19T09:54:45Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [May 19, 2025, 6:41pm UTC](https://forum.finsweet.com/t/the-cms-list-select-field-is-disappear-after-use-one-times/4842/2 "2025-05-19T18:41:26Z")

</div>

Hey @witchakorn.wat! Since List Filter can now filter multiple lists, all collection lists with the `fs-list-element = list` attribute will be filtered.

This can be fixed by adding an instance to a Common Parent element of the Custom Select and the list, or adding the instance definition to each element.

I’m showing both options below

1. Common Parent Element  
 ![Screenshot 2025-05-19 at 19.36.34](https://europe1.discourse-cdn.com/flex013/uploads/finsweet1/original/2X/4/47f9d3ffa3984e92b7d3c25131ee1a9e03245be7.jpeg)
2. Instance defined on each element  
 ![Screenshot 2025-05-19 at 19.39.08](https://europe1.discourse-cdn.com/flex013/uploads/finsweet1/original/2X/e/edbdb2abfb8fc7fe170dab27c1aee7e7995d3c12.jpeg)  
 ![Screenshot 2025-05-19 at 19.40.19](https://europe1.discourse-cdn.com/flex013/uploads/finsweet1/original/2X/1/199de4ba2defa094a425b6c94af3483dad0c75f9.jpeg)

---

_[View the full topic](https://forum.finsweet.com/t/the-cms-list-select-field-is-disappear-after-use-one-times/4842)._