New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Lookup fields give ambiguous error messages #149

Open

Bernardo-MG opened this issue Jun 11, 2015 · 0 comments

Assignees

Labels

Milestone

CWR File Parser

Collaborator

Bernardo-MG commented Jun 11, 2015

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.

Bernardo-MG added the enhancement label

Bernardo-MG self-assigned this

Bernardo-MG added this to the CWR File Parser milestone

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment