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

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... / oData urls not correct?
Small and medium business | Business Central, N...
Answered

oData urls not correct?

(0) ShareShare
ReportReport
Posted on by PhilDOakley 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? 

  • Suggested answer
    Marco Mels Profile Picture
    Marco Mels Microsoft Employee on at

    Hello,

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

    Thanks

  • PhilDOakley Profile Picture
    PhilDOakley 222 on at

    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.

  • PhilDOakley Profile Picture
    PhilDOakley 222 on at

    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 :-)

  • Suggested answer
    PhilDOakley Profile Picture
    PhilDOakley 222 on at

    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 :-)

  • Suggested answer
    Marco Mels Profile Picture
    Marco Mels Microsoft Employee on at

    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.

  • PhilDOakley Profile Picture
    PhilDOakley 222 on at

    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 :-)

  • Verified answer
    Marco Mels Profile Picture
    Marco Mels Microsoft Employee on at

    Great to hear this and thank you for confirmation!

    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

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the September Top 10 Community Leaders

These are the community rock stars!

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

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 728 Super User 2026 Season 2

#2
YUN ZHU Profile Picture

YUN ZHU 545 Super User 2026 Season 2

#3
AndrewThomas81 Profile Picture

AndrewThomas81 328 Super User 2026 Season 2

Last 30 days Overall leaderboard

Featured topics

Microsoft Training Manuals

Product updates

Dynamics 365 release plans