When nothing is entered in an Integer or Decimal field in an edit page, the field shows a zero value after saving the record. Is it possible to turn off this behavior, so that null is an acceptable answer for fields that are not required? For example, I don't want to test against a 0 limit when the requirement was that something pass or fail, but there is an option to enter a numerical limit if needed. Null is the appropriate answer, not 0, in this case.
Like
Dear Janine,
Such changes cannot be made at the application level, since a change in the default value is possible only at the database level, but such actions can adversely affect the operation of the application, since the application logic is not designed for the default NULL value for the Integer and Decimal columns.
If such changes are made to the database, this may lead to unforeseen errors, which in turn may affect the performance of individual application blocks or the entire system.
Regards,
Anastasia
Esther M,
No, it's not currently possible to perform this operation. Our R&D team is working on implementing this functionality, and their task is in the "Accepted" status. We will update you in the application's release notes once this functionality is implemented.
Hi Oleg, is there any update on this? A rough estimate of timeline or knowing if it's being actively worked on would be really good - it's constantly an issue that has to be worked around in various less-than-ideal ways that are sources for inconsistencies.
Harvey Adcock,
Hello,
The task is still in progress and the only workaround that currently exists is using the text column instead of a number. In case this number should be processed it can be done using type casting in formulas (or script tasks) of business processes.