Constraint problem
- Read more about Constraint problem
- 3 comments
- Log in or register to post comments
There seems to be a problem with the constraints in the generetaed XML schema. The unique check does not work, at least not all times.
2.1 Version
There seems to be a problem with the constraints in the generetaed XML schema. The unique check does not work, at least not all times.
When we generate DD for Elaborated Data and MeasureData there is a need to be able t configure not to geneate specific classes e.g. VMSFault. Enhance the profile configuration so that it is possible to exclude one or more classes.
If you have a model containing extensions and you choose de deselect a extension via the selection feature, the resulting schema will not validate. Error would be XXXExtensionType is missing.
When loading a selection from file, the tool only updates the current model with the selected elements from the selection. If you load several selection after each other it will become a mess. Before loadig the selection everything should be deselected.