Skip to content

Lookup fields give ambiguous error messages #149

@Bernardo-MG

Description

@Bernardo-MG

Currently if the lookup field content does not match the expected values the error just tells that the lookup field is missing.

The error message should say at least that this is a lookup field, and so is expecting a value from a list.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions