Troubleshooting
Problem
The purpose of this document is to provide documentation on the functionality of required fields and a required default value for existing records with null values in Database Configuration.
Resolving The Problem
When a user changes a database column from not required to required, and that column has existing instances of null data, Database Configuration will require a default value be provided to update the existing records with that value once the database was configured. The purpose of this functionality is to prevent future problems that could arise for a required field if a null value existed in existing records.
Going forward the field would be required and would prevent new records from being saved without a value.
It may not be appropriate for a default value to be specified. If this is the case, once the database wa configured successfully and the records containing null values were updated, it would be possible to go back and remove the default value, save, and reconfigure the database to remove the default value.
If you are making a field required that does not contain null values, you will not be prompted for a default value.
Historical Number
M04774
Product Synonym
MAXIMO
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21262178