View Issue Details

IDProjectCategoryView StatusLast Update
000986010000-003: Address SpaceSpecpublic2025-02-04 16:31
ReporterMatthias Damm Assigned ToJeff Harding  
PrioritynormalSeverityminorReproducibilityhave not tried
Status assignedResolutionopen 
Product Version1.05.03 
Summary0009860: Clarification needed for AllowNulls property
Description

From OPC UA Part 4 it was always invalid to have DataValue with a NULL Variant value with a Good StatusCode.

We recently added a dedicated Bad_NoValue StatusCode for the case where no value is provided 0007307 e.g. when loading variables from a nodeset that does not provide a value.

The AllowNulls property implies that a NULL Variant is a valid value for any DataType as long as the server has AllowNulls set to True.

As discussed in the working group F2F meeting today, this makes only sense for null-able DataTypes. The null-able DataTypes are defined in OPC UA Part 6.
But even then, (except for BaseDataType) the null value would be handled as the null-able DataType e.g. for a String DataType the server would accept a null String, not a null Variant.

Null Variant would only be valid for BaseDataType.

TagsNo tags attached.
Commit Version1.05.06 RC1
Fix Due Date2025-04-15

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2024-09-24 13:43 Matthias Damm New Issue
2025-02-04 16:30 Jim Luth Assigned To => Jeff Harding
2025-02-04 16:30 Jim Luth Status new => assigned
2025-02-04 16:31 Jim Luth Commit Version => 1.05.06 RC1
2025-02-04 16:31 Jim Luth Fix Due Date => 2025-04-15