Describe the bug
Inputting a number larger than "999999999" (10,000,000,000 and up) into the:startperiod, endperiod, startuncertainty, enduncertainty fields of a Chronostratigraphy record, then saving, causes an error.
While on the Chronostratigraphy Tree trying to create a new record, I had a Save Block warning message appear stating "Value must be a number" when I had 9000940390394039000 as my input, even though it is a number. Can not be reproduced consistently.
Additional context
Talked to @CarolineDenis and the range set as the max for these fields could be either something the user added in schema config or a value we have in our code.
Describe the bug Inputting a number larger than "999999999" (10,000,000,000 and up) into the:
startperiod
,endperiod
,startuncertainty
,enduncertainty
fields of a Chronostratigraphy record, then saving, causes an error.While on the Chronostratigraphy Tree trying to create a new record, I had a Save Block warning message appear stating "Value must be a number" when I had
9000940390394039000
as my input, even though it is a number. Can not be reproduced consistently.To Reproduce
startperiod
,endperiod
,startuncertainty
,enduncertainty
to a value > 999999999 (10000000000)Expected behavior Save should be blocked and a warning message stating the input is out of range should be displayed.
Evidence
https://github.com/user-attachments/assets/ff2234fb-e664-4981-a0b3-bd40a8ab7a2a
Crash Report Specify 7 Crash Report - 2024-09-23T18_14_25.318Z.txt
Additional context Talked to @CarolineDenis and the range set as the max for these fields could be either something the user added in schema config or a value we have in our code.
production
KUVertPaleo_2024_06_06
Cast Collection
spvertpaleoadmin
Specify 7 System Information - 2024-09-23T18_15_23.477Z.txt