View Issue Details

IDProjectCategoryView StatusLast Update
000988110000-008: Data AccessSpecpublic2024-10-10 15:32
ReporterPaul Hunkar Assigned To 
PriorityhighSeveritymajorReproducibilityalways
Status newResolutionopen 
Product Version1.05.00 
Summary0009881: MultiStateValueDiscreteType is broken
Description

When going from 1.04 to 1.05 the ValueRank of this was changed from scalar to Any - in the specification. In the nodeset it was Any, but the ValueAsText field is not an array, for if the overall value is an Array, the ValueAsText can not be filled in (only one bucket for it, instead of an Array)

The change in the spec to match what was in the nodeset was an incorrect fix - at this point we now have an vendor that is implement this as an array, and the ValueAsText property is not usable - At least the specification does not define what it should contain

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0005928 closedRandy Armstrong NodeSets, XSDs and Generated Code ValueRank mismatch between MultiStateDictionaryEntryDiscreteBaseType and its base type 

Activities

Paul Hunkar

2024-10-10 15:30

developer   ~0021875

At this point reverting the change in 1.05 to make it an Any does not make sense and will cause more issue then it would solve, but that in text we can restrict the value of the MultiStateValueDiscrete to be only a scalar. explaining that this was a problem in the original Nodeset , but since ValueAsText can not report an Array, and this is the field that is most commonly subscribed to when using this type, any setting other then an scalar is not allowed.

Issue History

Date Modified Username Field Change
2024-10-10 15:18 Paul Hunkar New Issue
2024-10-10 15:19 Paul Hunkar Relationship added related to 0005928
2024-10-10 15:30 Paul Hunkar Note Added: 0021875
2024-10-10 15:32 Paul Hunkar Summary MujltistateValueDiscreteType is broken => MultiStateValueDiscreteType is broken