Is it possible to create a multi-select lookup from entity metadata in Freedom UI?

Hello ,

I am working on a Freedom UI modal page where I need to display entity schema metadata (field list) and allow the user to select two or more fields from that metadata.

Requirement

  • Source data is entity metadata (not business records)
  • User should be able to select multiple fields
  • Selection should be limited strictly to the metadata values
  • The control should remain interactive (not fully disabled)

What I have tried

  • crt.DataGrid with multi-row selection (facing stability/UX limitations)
  • Custom HTML / repeater components (not supported in Freedom UI)
  • crt.Input with control: "multiSelect"
    • readonly: true → control becomes fully locked
    • enabled: false → selection not possible

Questions

  1. Is it supported to create a multi-select lookup or multi-select input whose options come from entity schema metadata in Freedom UI?
  2. What is the recommended pattern to:
    • prevent free text entry
    • allow only selection from predefined metadata values
    • support selecting multiple values
  3. Are there any OOTB components or best practices for metadata-driven selection in Freedom UI?

Any guidance or recommended approach would be greatly appreciated.

Thanks in advance!

Like 2

Like

1 comments

Hello,
Your approach sound very overcomplicated. First of all, the whole Freedom UI interface doesn't intended to work directly with metadata, therefore, we cannot guaranty the stable work of any input field, that include multiselect. The short answer would be no, there are no options to work with metadata in multiselect.
In this situation, we can recommend you two approaches, but, both of them require you to create some sort of layer between your page and metadata. Basically, you need to store values from the metadata in a dedicated object, then, the data from this object can be accessed on the modal page as any other table. After that, you either can:
1) Create a normal multiselect lookup:
2) Instead of it, store the values in the detail.

Show all comments