Something is wrong with your installation as you have somehow combined two different fields

There should be a show status AND a use in subform field

@brianteeman No its just a smaller screen its actually on the second row and its mac so it opens the native select dropdown. Actually is right behind of it. Should it say - Use in Subform - or something like - Select ... - ?

@brianteeman No its just a smaller screen its actually on the second row and its mac so it opens the native select dropdown. Actually is right behind of it. Should it say - Use in Subform - or something like - Select ... - ? Whats the difference in meaning between Use in subform and Only in subform?

Use in subform is a heading just like Select Language is a heading - it has no meaning and no value

Use in subform is a heading just like Select Language is a heading - it has no meaning and no value

I think this could perhaps be made a little clearer from a UX perspective.

My understanding is that there are really three states here:

• Select Form Type — placeholder
• Any Form — the field can be used normally in any form
• Only in Subform — the field is restricted to Subforms

The current wording “Use in Subform” could potentially be interpreted as simply allowing the field to be used in a Subform, while “Only Use in Subform” communicates a restriction to Subforms.

With that in mind, perhaps the select could describe the form scope/availability instead, for example:

Form Type

Select Form Type
Any Form
Only in Subform

I think this would make the distinction a little more explicit and aligned how the other filters work already, while still leaving the final wording/design choice open to the maintainers.

I would probably change the placeholder to

• • Select Field Usage -

I would probably change the placeholder to
- Select Field Usage -

Please test #48264

I have tested this item successfully on c3d78cf.
The updated filter wording is displayed correctly and the filter behaves as expected.

this can be closed as it was solved with #48264 n