Description of the limitation and why it is relevant to address
As an application developer i would like to use the ChildEntityOptionField and ChildEntityMultiSelectField for childs of other entities, so not only from the current entity.
I think this is relevant for the VIKTOR platform because this removes the need to use the Viktor API() to generate the options myself in a normal OptionField.
Submitter proposed design (optional)
Add a ‘parent_entity_id’ to the parameters of these fields.
In general, I think api functions/fields should return entity objects (possibly without params) instead of entity ids.
Current workarounds
Use the API() myself to get the entities and put them in a normal OptionField.