We're updating the issue view to help you get more done. 

OneToMany configurator fails if config field is called "value"

Description

Because of the way the configurator was built on top of the standard object picker/uberselect, the property `value` was reserved for use by the control, and so would be ignored if it appeared in the configurator form.

However, it may be that it is not possible to specify the name of the field - some applications work against a pre-defined database model - so we should find a way to overcome this restriction.

Environment

None

Status

Assignee

Seb Duggan

Reporter

Seb Duggan

Labels

None

Accepted

Yes

Fix versions

Priority

Medium