Hello,
A partner is trying to post an invoice via web service and is getting an error because of an automation component: XMLHttpConn in a specific codeunit. I'm wondering about remaking it's implementation in .NET since it could solve this problem and the webclient limitations over automation also.
I thought about System.Xml.XmlDocument but the problem is occurring in the following code:
IF ISCLEAR(XMLHttpConn) THEN
CREATE(XMLHttpConn,TRUE,TRUE);
So I would like to know if anyone know a .net component that could replace XMLHttpConn in the connection scope.
thanks in advance.
0
Comments
Yes you can pretty much directly replace the automations using .NET. We were using MSXML03 in our Classic product and have rewritten everthing in DotNet using the System.Xml library.
If you're using DotNet variables you'll need to initialise the variable slightly differently.
For XMLDocument you can use the constructor e.g;
XMLDoc := XMLDoc.XmlDocument();
You can check to see if the DotNet variable has been initialised using ISNULL.
e.g. IF ISNULL(XMLDoc) THEN...
Have a look at System.Net.HttpWebRequest for your XMLHttpConn variable.