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.
Here I am after a while. I’ve just started new video series about great new product Dynamics 365 Sales Professional. I’ll create probably dozens of different videos about functionalities and configuration, but in this first one I’ll start with how to create a trial environment.
If you didn’t already hear for this solution, just to know this is the great Microsoft CRM solution especially for small and midsize organizations and it is available as full SaaS solution.
Now, I hope you will enjoy in this first video, and I’ll notify you as soon as I publish the new one:
If you’ve already read my previous article about introduction in BC and Talent integration, then you probably expect the next part. I cannot put everything in one blogpost as it will be a huge one and it can be confused to track all details, so I decided to write it in parts. Today, I’ll write how to prepare Business Central and Talent and how to locate data/entities you will handle with.
As I’ve already mentioned in previous post, as we don’t need all HR capabilities in Business Central and we will use all of them in Talent, we will enter data directly to Talent and move to BC only data necessary for other areas in BC. We will move data to Employee table as this table will be used in other parts of BC.
As we will create new employees in Talent, we need to configure No. Series to be fit with Talent requirements. If you want automatic numbers, you need to be careful and to make it exactly the same as in Talent, but I’ll recommend to configure Employee number series as Manual Nos.; this will keep the same numbers in Business Central as we have in Talent and you will avoid all potential risks.
As connectors with Business Central, we will use API’s. Employee table, for example already exists as an API, but if you would like to connect something more, you will probably have to create custom API and custom connector.
What we can synchronize? As I said, minimum we need in BC is Employee table. And you need to find entity as a source in CDS (I’ll explain later). You can connect entities as following:
If you want to find all details about Workers data in Talent, the best is to use the following Worker entity relationship model. But the best is to integrate only what is really necessary… only what you will really use in Business Central.
As we need to locate Talent entities, you need to open list of CDS entities in PowerApps platform (you don’t need to do nothing in Talent environment and you can use it only if it will help you to better understand environment; for all integration purpose you will use CDS – PowerApp). When you open PowerApps web page, you need to choose environment created for Talent.
After that, you need to open Data and Find Entities. In Entities, you can easily find Worker entity as this is a place where we can find our information.
Opening this entity, you can address all necessary fields you want to use in integration. And how to do it, you will see in the following post.
NAV TechDays 2019 has just finished a few days ago and I can
say this was amazing event and again the biggest one – with 1452 attendees. As
I promised the last year, I prepared session this time and made it together
with an MVP Renato Fajdiga. I hope to see you next year again.
In a meantime, all sessions from the first day are already published and I want to have all of them on the one place. As soon as we have sessions from the second day published, I’ll add them. There are all of them:
Opening Keynote
The road from C/AL to AL
Development Methodologies for the future
How to run faster in SaaS
Unlocking new integration potential for 365 BC with Azure Event Grid and Azure Integration
Give Business Central access to your data files
Control Add in development supercharged
Developing for Modern clients
Using Docker and the ContainerHelper to convert your C/AL solution to an AL solution
#MSDyn365BC new Era of Integration: Intelligent Edge, SmartLists, Azure Service Bus and more!
This fall I’ll be active and attend to four conferences as lecturer. If you want to see some of my lectures or to meet me, register for some of these events:
Totovic Dynamics 365 Blog 