Kbase P57246: Dyn 2.1A: Add record, many fields get a ?, because of missin
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/12/2003 |
|
Status: Unverified
FACT(s) (Environment):
Dynamics 2.1A
SYMPTOM(s):
Adding/creating new record
Decimal or integer have unknown value (question mark, ?) instead of expected 0
Date fields have unknown value (blank) instead of expected today as defined in schema
CHANGE:
Upgraded to Dynamics 2.1A
CAUSE:
Known issue. In 2.1A, we now rely more intensively on the defaultValue attribute than in the past. Now, when an entity field has not this defaultValue attribute defined, then it inherits from the defaultValue of the DataField class, which is blank. (good value for character fields). This results in an unknown value for decimal, integer and date fields.
Normally, the entity import should define the defaultValue attribute for an entity field as soon as its schema INITIAL-VALUE is defined as not blank (so it does for decimal, integer and date that cannot be blank). This is what happens in 2.1A for sure, and then it does not inherits from the data field class.
However, few cases have been reported with repositories that were upgraded from earlier versions (such as 1.0A), and that did not have a defaultValue defined for decimal, integer and date fields.
In this case, doing an entity import without checking the 'overwrite all attribute from schema' toggle-box (unchecked by default) does not solve the problem
FIX:
Do an entity import with the 'overwrite all attribute from schema' toggle-box checked, or manually define the defaultValue attribute for the entity data field.
See Progress Solution P58788 How to report entity fields that do not have a given attribute defined at the master level