Difference between custom api and standard api

(0) Share

Report

Posted on by garydee

I've played around with the standard api's available out of the box and I can get all available methods to work ok (get,post,patch and delete), I tested on the customer table. I've now created a custom web service via the Business central web portal exposing the exact same table (customer table). The get method works fine, however the column names returned are different. For some reason using the custom end point the address field as well as the id field are not returned. When trying to do a patch using the custom web service I get the following error: "BadRequest_MethodNotAllowed","message":"Entity does not support modifying data.

My question is two-fold: why are the fields returned different between the two api calls and is this the cause of the patch method not working?

I have the same question (0)

All responses (3)

Answers (1)

Suggested answer

JAngle 133 on at

Like (1)

Report

I assume you have used web services page in BC to do this? This is not really part of the api in the same way as the standard api pages. You can create custom ones if you can code.

If I am right about it being web services you need to pick pages that play out correctly in the regular UI. So for customers pick page 21 as you can do all the CRUD commands. I assume you chose page 22 which is read only. All fields will be captioned as they are in the UI albeit with no spaces

Was this reply helpful? Yes No
Verified answer

YUN ZHU 95,331 Super User 2025 Season 2 on at

Like (0)

Report

Hi, For the first question, in fact, the page you use in the Standard API and the page you use in the Web Service are not the same page. So the fields are not the same.

Tables cannot be published directly in BC, this has to go through page. (In addition, when you access Web Service, it is not actually API access, but Odata or Soap.)

I believe you have selected a standard page in the Web Service.

For example:

Customers: page ID 22.

But in api, page id 5471

For the second question, I agree with Josh.

So if the fields do not meet your needs, you should consider creating a new page yourself, publishing to a Web Service, or creating a new API page.

Hope this will help.

Thanks.

ZHU

Was this reply helpful? Yes No
garydee 86 on at

Like (0)

Report

That is really helpful thanks ZHU.

Was this reply helpful? Yes No