Hi, in closed issue #554 is stated, that IsNull is not needed for Native XML Types. I disagree.
Situation:
procedure having parameter of type XmlNode, how can I inside the procedure decide if the XmlNode is empty (not initialized) or not? To keep in line with issue #554 I will need to add another parameter, which will tell me if XmlNode was returned in previous step or not. This is not good...
Interesting is, that in case of JsonValue there is property/method IsNull.
In C/AL we were able to use IsClear for Automations, IsNull for DotNet and FORMAT(var)='' for native variables. I still see the need for IsNull for native AL types like XmlDocument, XmlNode etc.
kine
All 2 comments
In the case of JsonValue, IsNull, means that the value represents a JSON null, it does not mean the variable is not initialized.
Thank you for the input! We will take it into account for a future update.
atoader
on 12 Mar 2018
In any case, it should be a humble wishto have ISClear/IsNull etc.
It will help CAL Developers move to AL and do our many upgrades :)
JSebastianN
on 24 May 2018
Related issues
mjmatthiesen
路
25Comments
navdotnetreqs
路
21Comments
BartPermentier
路
23Comments
Gallimathias
路
38Comments
kine
路
36Comments
Most helpful comment
In the case of JsonValue, IsNull, means that the value represents a JSON null, it does not mean the variable is not initialized.
Thank you for the input! We will take it into account for a future update.