A persistent, multiselect custom field that works correctly on a page doesn't show up as an option in that page's header-level search filter dropdown, even though other (non-multiselect) custom fields on the same page do.

All FAQ questions / Platform, Aurena, and customization

Answer

This is a confirmed limitation of the Custom Objects framework in the web client — multiselect custom fields specifically don't appear as selectable search-filter options, even when everything else about the field (syncing, display, editing) works correctly; there's no configuration workaround to force a multiselect custom field into the filter dropdown.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Platform, Aurena, and customization questions