Hello
Before version 8.3.0 if a numeric field is required the value couldn't be zero: zero was considered "null", since numeric values on database have 0 as default value and don't allow null values. In a Freedom UI FormPage a required number had to be NOT zero.
Starting from version 8.3.0 if a required numeric field has value ZERO it's OK. Only if the field cell is left blank the FormPage warns the user that the field is required. This logic is completely different from the one that has been used for years before 8.3.0: is this a bug and will be fixed to restore the previous behaviour?
I think this is a bug since on database numeric fields still have zero as default value and are set as Not Null, then there's no way to leave null a numeric field, even if it's not required.
Is there some ways to restore the previous behaviour without writing a field validator in javascript in all existing pages?
Thanks
Like
Confirmed this is still the case in 8.3.1. Not sure what functionality the "required" flag now performs for numeric fields, since as you say Creatio doesn't allow actual null values for numeric fields and defaults them to zero. I wonder if this indicates that we might be able to differentiate between zero and null in future - I hope so!
Hi Harvey ,
I don't know if in future null values will be available for numeric fields, but all existing entities have already been created not allowing null values.
The actual numeric fields management on the user interface is not consistent with the database structure, then I hope Creatio will fix this issue very soon.
Hello Massimilliano,
We have tested this behavior on site with versions lower than 8.3.0 and the validation allows 0 to be saved for the field, please see testing below:
Could you please provide us with more information on how to reproduce the issue, if there is something we are missing?
Thank you in advance!
Hello Alina ,
Our customers reported the issue after 8.3.0 upgrade, then it's possible the issue was already present in 8.2.2.
In any case, regardless the origin is version 8.2.2 or 8.3.0, it's an issue and our customers are asking for a fix.
Thank you