Business Central API’s and Available Methods

If you use API’s in Business Central, probably you found some limitations in methods, depending on API to API. Sometimes you can do more, sometime less. For example, with Accounts you can use only GET method (I still don’t understand why?), and so on…

You can find details about all of them here, but I prefer to have everything on one place as it will be easier to decide if I would use standard API or eventually I need to create the custom one. Because of that, I’ve made this matrix with all standard API’s and methods you can use with them:

Except these limitations, it would be nice to know that you have some other limits as well and they are important if you want to use API’s in some solutions. Even if those limits are high, they are still limits. For example, you can have maximum 600 requests per minute in production environment and 300 in sandbox. Complete list of limits is here.

And what is also important? If you are using those API’s through Power Platform (or Logic Apps) connectors, you should understand their actions and parameters. All details can be found here, but there is a table for better understanding:

It is important to mention that all that information are subject of change.

Translation in Extensions in NAV / D365 Tenerife

Today is announced November Update for new NAV Development Environment. There a lot of good things in this preview, but by my opinion one thing stands out. Maybe I think so, because I’m from countries where Microsoft doesn’t prepare official localization, and because of that partners need to do it by them self.

Anyway, from this update, it is possible to add translation to Extensions. This is the first step in providing localization via extensions. I don’t want to say that everything else is simplify, but this was necessary feature to do it. OK, translation will not be made as before, and now we need to accept different approach, but feature is here.

translation.png

I don’t want to write about this and other features in detail, because this is already published on Microsoft official blog and you can read there.