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

Notifications

Announcements

No record found.

Community site session details

Community site session details

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

There are multiple services with same name and object name. How are they different and how to decide which one to use?

(0) ShareShare
ReportReport
Posted on by 25

For example, for vendors service, there are many services named vendors with different Object Id's as seen below

Screenshot-2020_2D00_08_2D00_06-at-12.24.50-PM.png

My question is what is the difference between them? How are they categorised or what distinguished from another?
Finally which service should I be using? 

And I noticed the API response of each service is a bit different.
And what exactly is workflowVendor object?
Is there any kind of documentation at all about this?

I have the same question (0)
  • Suggested answer
    JAngle Profile Picture
    133 on at

    As well as being web services most of them are designed to be used in the regular UI. The difference will therefore be the intended use in the UI. For example a vendor list page will show less information than a vendor card page. If you use the page inspection tool on a page it will tell you the ID. This way as you’re making your way around the application and find an applicable page you can publish it as a web service.

    The workflow one is for use with workflow in power automate.

    Doubt you will find specific documentation on this but perhaps someone else in the community has something they can dig out.

  • star lord Profile Picture
    25 on at

    Yeah, would definitely like more info on this.

    Also, the Business central REST API (which is readily available and not the web service which needs to be manually published) is missing few end points but are available as a web service

    For example, purchaseOrders is not exposed in the REST api bbut is available as web service to be exposed

  • Suggested answer
    JAngle Profile Picture
    133 on at

    In general I would overlook the api given it can’t be extended and is lacking. With web services you can extend standard pages and you get the data and it is easier to develop a none api page as you need less triggers. OData filtering is simple enough to adopt for GET commands so web services, for me are used more often.

    If I was working on an integration scenario where a 3rd party needs access then I would use the api as it’s more restrictive. When it is your system you can move between the two but I’d more regularly opt for web services.

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…

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

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 2,664

#2
YUN ZHU Profile Picture

YUN ZHU 960 Super User 2025 Season 2

#3
Jainam M. Kothari Profile Picture

Jainam M. Kothari 773 Super User 2025 Season 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans