Support for DataTypeDictionary, which contains the decoding information for custom types is planned only for the next SDK release. But we will keep you updated, when a beta implementation would be available.

So far, the SDK can only decode types that are modelled via code generation (preferably).

Hopefully in 2.3 we can offer some support for it, however I cannot guarantee that at the moment.

(If you wonder, Jouni’s earlier answer meant 2.3, which is still in development)

A rough estimate for 2.3 is start of February 2017, however, it’s too early to promise anything right now.

I suppose I should note that this feature is not on very high priority as the specification 1.04 (which is draft / not yet released) will contain a new way (most likely new attribute) to describe custom structure meta directly via addressspace/ua types, which will effectively replace the datadictionary system.

Also our understanding is that most of the customers can use codegen for custom structures.

Currently what I mentioned with 2.3 in above posts was changed to be 3.0. An issue regarding handing diagnostics came up with the compliance testing and the result became 2.3.

There were some bugs regarding loading the typedictionarys from the Nodeset XMLs, they are fixed by the stack that comes with SDK 2.3.2 (https://downloads.prosysopc.com/opcua/release_notes2.3.2-781.html).

I hope we can make a public beta of 3.0 soon and release it before the end of 2017.
Currently in the development tree (for 3.0) we have a TypeDictionary class that takes a UaClient and can decode given ExtensionObjects to DynamicStructures, which does act like a map. However it is something you have to specifically create and call at the moment.

– Bjarne