View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000988110000-008: Data AccessSpecpublic2024-10-10 15:182024-10-29 15:14
ReporterPaul Hunkar Assigned ToKarl Deiretsbacher  
PriorityhighSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product Version1.05.00 
Fixed in Version1.05.04 
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.

Alexander Allmendinger

2024-10-16 09:53

developer   ~0021898

During the UA Meeting on 15th of October 2024 it was discussed to add wording for the case where the value rank is not scalar. In this case the group thinks that having the ValueAsText set to a NULL LocalizedText will be the best solution.

Karl Deiretsbacher

2024-10-22 15:22

developer   ~0021927

Changed the description of ValueAsText in 1.05.04 as follows:
"If the Value is scalar, the ValueAsText Property provides the localized text representation of the enumeration value. It can be used by Clients only interested in displaying the text to subscribe to the Property instead of the Value Attribute. If the Value is not scalar then ValueAsText should be Null. In that case, Clients can use the EnumValues Property to lookup the display information."

Jim Luth

2024-10-29 15:14

administrator   ~0021959

Agreed to changes in web meeting.

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
2024-10-16 09:53 Alexander Allmendinger Note Added: 0021898
2024-10-16 11:00 Jim Luth Assigned To => Karl Deiretsbacher
2024-10-16 11:00 Jim Luth Status new => assigned
2024-10-22 15:22 Karl Deiretsbacher Status assigned => resolved
2024-10-22 15:22 Karl Deiretsbacher Resolution open => fixed
2024-10-22 15:22 Karl Deiretsbacher Note Added: 0021927
2024-10-29 15:14 Jim Luth Status resolved => closed
2024-10-29 15:14 Jim Luth Fixed in Version => 1.05.04
2024-10-29 15:14 Jim Luth Note Added: 0021959