Dynamicweb NAV Connector

Søren Heide Larsen

Posted on 19/11/2019 09:13:02

Hi,

We have a customer that uses the Dynamicweb NAV Connector and we want to get to solutions up and running, each having a different connector but to the same NAV Company.

The ideal way would be to offer two different web-services, so the logic does not interfere with each other, but when we try to change the NavEndpoint to another webservice, we get the following error.

Any ideas how to fix this?

System.ServiceModel.FaultException: Parameter request in method Process in service DWWebService2 is null!

Server stack trace:

at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)

at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)

at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)

at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:

at Dynamicweb.DataIntegration.Integration.ERPIntegration.ErpServiceCaller.SendRequest(DynamicwebServiceClient client, String secret, String requestText)

at Dynamicweb.DataIntegration.Integration.ERPIntegration.ErpServiceCaller.GetDataFromRequestString(String endpoint, String secret, String requestXML)

Replies

Dmitriy Benyuk

Posted on 19/11/2019 09:24:57

Hi Søren,
it looks like your second webservice is missing parameter "Request".
Can you check your NAV code unit and your second webservice code for Process method?
It should look like that:
Process(VAR Request : BigText)

Best regards, Dmitrij

Søren Heide Larsen

Posted on 19/11/2019 10:03:20

Hi Dmitriy,

Thank you for the fast response.

It has that method (see attached WSDL). We have also tried to rename the existing working DWWebService to DWWebService2 and calling that, which results in the same error, so i am pritty sure the web-service is correct.

/Søren

web-service-description.xml

Dmitriy Benyuk

Posted on 19/11/2019 10:17:46

Hi Søren,
problem is that NAV connector uses the compiled service reference which is set to Namespace="urn:microsoft-dynamics-schemas/codeunit/DWWebService".
If you have an access to the source code of the NAV connector project from DynamicwebConnectorService solution you could copy/create your own NAV connector and point it to your second webservice in the service reference and compile it with a new name so the DynamicwebService can then reference your new NAV connector in its settings.

Best regards, Dmitrij