Skip to main content

Notifications

Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Answered

oData urls not correct?

(0) ShareShare
ReportReport
Posted on by 222

I have a new install of BC on prem V16 and when I go to the web services card the urls for the odata do not appear to be correct. 

I have 

https://publicURL:7048/OData/ODataV4/Company('Delph%20Manchester')/AccountantPortalActivityCues

If I cllick on this I get a 404 error so I am thinking one of the items in my config is wrong. Does this url look correct? 

  • Verified answer
    Marco Mels Profile Picture
    on at
    RE: oData urls not correct?

    Great to hear this and thank you for confirmation!

    Thanks.

  • PhilDOakley Profile Picture
    222 on at
    RE: oData urls not correct?

    Marco

    The public URL is correct. It was just the OData that was causing the issue. I looked in the BC manager and in the oData section there is a url. This was set as https://publicURL:7048/OData

    I changed this to https://publicURL:7048/bc160 and restarted the nst. The web services show the change and a click brings up the xml response after logging in.

    All is good now and thanks for pointing me in the right direction :-)

  • Suggested answer
    Marco Mels Profile Picture
    on at
    RE: oData urls not correct?

    Hello,

    It is now displaying correctly or not displaying correctly? In a multi tenant setting with a rewrite host name rule name, the PublicODataBaseUrl may be different from what is being shown in web services.

    E.g.:

    PublicWebBaseUrl = servername.domainname.com:7048/.../

    Rewrite host name enabled in IIS and alternate ID set on the tenant to nav.domainname.com.

    Then web services may show the following:

    nav.domainname.com:7048/.../

    That is still correct.

    Thanks a lot.

  • Suggested answer
    PhilDOakley Profile Picture
    222 on at
    RE: oData urls not correct?

    I found that the setting I need to change is in the oData URL in BC admin screen. I may have set this UR incorrectly at install as this had oData at the end. I have changed this and it is not displaying correctly in the web services screen :-)

  • PhilDOakley Profile Picture
    222 on at
    RE: oData urls not correct?

    I have overtyped the odata with the instance name of bc160 and that now displays correctly. I just need to make this correct in BC so it is picked up in the web services screen and I'm done :-)

  • PhilDOakley Profile Picture
    222 on at
    RE: oData urls not correct?

    The BC instance is BC160 so should that be where the odata is? If so where is this being pulled from and I can change it.

  • Suggested answer
    Marco Mels Profile Picture
    on at
    RE: oData urls not correct?

    Hello,

    After port, there is OData and after that there is another ODataV4. Is the Instance name OData or is this incorrect?

    Thanks

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

🌸 Community Spring Festival 2025 Challenge 🌸

WIN Power Platform Community Conference 2025 tickets!

Jonas ”Jones” Melgaard – Community Spotlight

We are honored to recognize Jonas "Jones" Melgaard as our April 2025…

Kudos to the March Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 294,033 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 232,854 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,158 Moderator

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans