AnsweredAssumed Answered

Returned AFValue type not always correct

Question asked by Dries.Verhees on Jun 8, 2016
Latest reply on Jun 9, 2016 by Dries.Verhees

Hi everybody,


I have noticed that in my implementation, the type in AFValue is not always in line with the type configured in AF.

I have one attribute (Sinusoid) which is configured as a double.



I have created the following code (for testing purpose), where I execute two interpolated data calls.


The type is correct for the call with only one attribute, but the type is incorrect (single instead of double) for the call with two attributes.


Is this the expected behavior? I'm using AF SDK