Forum Discussion
Also I noticed one thing that this field in the ItemTypes table already has the default value set as "8DF7037346A64816B8BBD8700AFCFE15", so why do I need to add this value ?
The new RE application is built off of the same framework that powers our Technical Documentation application. These kinds of ItemTypes require a schema in order to define what the format of the document should be. In RE 11.0R1, all of the requirements default to a particular schema specific to requirements. This property is not configurable by default.
The reason it needs to be defined in your AML despite having a default value is that default values are not applied until after the onBeforeAdd server event has run. Because of this, the property still has a blank value in the onBeforeAdd server event which is causing the error you are seeing when a snippet of code attempts to access that value.
Typically, you can see which properties on an ItemType are needed to create it by checking which properties have the Required flag set to true. However, this is a special case because the error is not being thrown by the standard add logic. It's instead being thrown in the onBeforeAdd server event.
I've filed an issue internally to report this behavior. It does make sense to not need to define this property in your AML because of the default value.
Chris