You need to make sure your Attribute is set as Searchable in Order to enable the Filter to appear as an option:

The default value on Page Designer, barring any context overrides, should be inherited from the Attribute definition itself, but I’m not sure that actually works, because even if I set a custom attribute as non searchable, when adding it to an entity, I can still filter on it by default unless I specificy Searchable as False in the page designer

@SimonTestard, thank you for your answer .
Indeed, my Searchable flag was set as default. Unfortunately, setting it to true did not help in my case. Maybe the reason is that I’m using multivalue enumeration? I completely forgot about it, and it is probably an important detail.

Therefore, my question should be rather: how to filter multivalue custom enumeration?

By the way I think setting the Searchable flag in the custom attribute definition probably creates an index in the database and speeds up searching. Without an index, search is still possible. Therefore, to avoid confusion the name should be IsIndexed, SearchOptimized, FastSearch, ...

I don’t think the Searchable flag in the custom attribute creates an index, simply because there is another flag to do that ;)

In Apps 10, defining a custom attribute as searchable made it so that you could use it in the search dialog as a potential filter:

It’s necessary to make the field Searchable for it to appear here, basically:

In Cloud, I’m unsure which purpose it serves, as you can definitely do a search on that field in the search box as long as it’s searchable through the designer, it doesn’t seem to actually make it default to False at designer level (this might be a bug to be honest).

For example my field testenum2 is set up as Non Searchable, but as long as I add it to the designer context, I can search for it (both on the main search, and the list search itself):

I can however confirm to you, testing on 23R2, that Multi selection Custom Enumerations indeed do not seem to support searchable filters.

Whether I enforce searchable or not, I cannot get either the top level search or the list search to allow a filter on it. This might be a bug but I think it’s more likely that it’s a technical limitation somehow.

If you try to hack it in the main advanced search by forcing a search on the multienum field, you get the following message:

So I think it’s simply not allowed to search/filter collection elements unfortunately ?

In summary:

1. Custom multi-select enumerations do not appear to support search filters.

2. It is unclear in IFS Cloud what the purpose of the Search flag in the custom attribute definition is.

 

 Regarding (1) I cannot see filter even for Core (not Custom) multi-select enumerations:

Regarding (2), the search flag in the custom attribute definition may be a leftover from App10 and it is possible it is no longer used in IFS Cloud.
@SimonTestard, you easily convinced me it is not for indexing purposes .
Thank you for your help.