web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Small and medium business | Business Central, N... / BC21 OnPrem SOAP WebSe...
Small and medium business | Business Central, N...
Answered

BC21 OnPrem SOAP WebService Wrong Definition part

(0) ShareShare
ReportReport
Posted on by JuliettWhiskey81 5

Hi,

one of our departments is still relying on a SOAP webservice. We are using this WebService since NAV2018.

In NAV2018 and BC18 the SOAP webservice returns the following in the definition part:

    <service name="MyService">
        <port name="MyService_Port" binding="tns:MyService_Binding">
            <address location="https://[FQDN]:7047/[InstanceName]/WS/[CompanyName]/Codeunit/MyService" xmlns="">schemas.xmlsoap.org/.../"/>
        </port>
    </service>

Now in BC21 this changed to:

    <service name="MyService">
        <port name="MyService_Port" binding="tns:MyService_Binding">
            <address location="https://[FQDN]:7047/[CompanyName]/Codeunit/MyService" xmlns="">schemas.xmlsoap.org/.../"/>
        </port>
    </service>
So the InstanceName is missing in the address location and in my opinion this is a wrong definition. Is there an option (maybe in the BC service configuration) to get the InstanceName back to the definition?
Thanks
I have the same question (0)
  • Suggested answer
    Marco Mels Profile Picture
    Marco Mels on at

    Hello,

    Thank you for this message. We are working with a partner that reported the same issue. The partner mentioned the issue can be considered as mitigated when using a hosts file (location: c:\windows\system32\drivers\etc). You can add the following line in the hosts file:

    127.0.0.1   FQDN

    You can also clear the field PublicSOAPBaseUrl in the customsettings.config file, this was our last suggestion to try out. We currently do not have an internal repro so we do not know why this is happening.

    Thank you.

  • Suggested answer
    DAnny3211 Profile Picture
    DAnny3211 11,397 on at

    hi

    look this

    learn.microsoft.com/.../soap-web-services

    DAniele

  • Suggested answer
    JuliettWhiskey81 Profile Picture
    JuliettWhiskey81 5 on at

    Hi Marco,

    thanks for your feedback. Removing the PublicSOAPBaseUrl worked for me. Thank you so much for sharing this info.

  • JuliettWhiskey81 Profile Picture
    JuliettWhiskey81 5 on at

    Hi Daniele,

    I'm absolutely able to read documentation and did this before opening this thread. But where is the solution for my problem in your link?

    @thecommunity: If you need an example for an totally useless answer: here you are!

  • Verified answer
    Marco Mels Profile Picture
    Marco Mels on at

    Hi,

    Understood, thanks. I have a bug open on this issue, so this feedback that it is resolved this way really helps.

    Thank you.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 2,066

#2
YUN ZHU Profile Picture

YUN ZHU 658 Super User 2025 Season 2

#3
Sumit Singh Profile Picture

Sumit Singh 595

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans