WSDL Import location is different from Soap address for Custom webservice in Non development environment

(0) Share

Report

Posted on by rama.krishna.tannee...

104

Hi All,

I have a strange issue while using D365FO Custom webservice. In a Non development environment, the WSDL import location url is different from the Soap address.

for example. My Soap URL is "">ax.test.xxxxxxxxxxxx.de/.../xxxxxxxxxOrderServices

if we look at the <wsdl:import namespace="http://tempuri.org" location="ax.test.xxxxxxxxxxxx.de/.../xxxxxxxxxOrderServices"/> is different from bottom Soap Address <soap:address location="ax.test.xxxxxxxxxxxx.de/.../xxxxxxxxxOrderServices"/>. The Namespace/AXSF in the Url is replaced by a big SID.

This issue is only with the Non development environments like TEST and PROD. But in Dev Environments, both the Urls are same.

Kindly let me know how to fix this issue and what is the root cause behind this issue.

Thanks in advance!

Ramakrishna Tanneeru.

*This post is locked for comments

I have the same question (0)

All responses (1)

Answers (0)

Suggested answer

Anup Shah MSFT on at

Like (0)

Report

This is normal. the production and sandbox on-premises servers use service fabric and will always have /namespace/AXSF andded to the endpoints.

Was this reply helpful? Yes No