Fixed

long schema field uneditable after incorrect data format used for max value validator

12 years ago • updated by 9 years ago • 2

I set up a "long" schema field, with a max range of "-50.3". An error appears on the connector screen:

Incorrect value max attribute in <Extended max="-50.3" xmlns="" />

This error also appears if I attempt to update the schema field with a full stack trace, and does not let me update the field definition.

As an improvement, the message should tell the user which field contains the wrong validator.

Vote

Discovered while testing 2.5.1 of the test document.

This also happens if you enter a number too large in the validator for a "single" value type.