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

spinner validation is wrong when minvalue=0 and no maxvalue

Description

In this constellation in the object definition the validation of the spinner is wrong:

property name="anz" type="numeric" dbtype="varchar" control="spinner" minvalue="0";

Regardless of the value, the validation error message is "Must be at least 0".

This only happens, when the minvalue="0" and there's no maxvalue defined. With minvalue > 0 and a maxvalue everything is fine.

Environment

None

Status

Assignee

Unassigned

Reporter

Michael Hnat

Labels

None

Accepted

Yes

Fix versions

Affects versions

10.8.69

Priority

Medium