This is the third post in a series about batch calls with Business Central. If you haven’t read the the other posts, then I recommend to do so. You’ll find the first post about basic operations with batch calls here. The second post about error handling and transactions can be found here.
This is the second post in a batch series about batch calls with Business Central APIs. You can find the first one about the basic operations with batch calls here. In this post, I want to cover one of the most frequently asked questions about batch calls: what happens if one of the operations runs into an error? Will it stop further execution, will the already processed operations be rolled back? Let’s have a look.
A while ago I wrote about deep inserts with Business Central APIs. And I promised to write about batch calls too, so it’s about time to live up to that. 😀 Actually, I did some online sessions about it, like this one for DynamicsCon and also for Directions 2020. But I think it is still worthy to write it down.
I have added Codeunit ISI Events to call the subscriber.
IsCustomerExist will first check if contact exists or not, if it doesnot exist then it will proceed further and create contact and function CreateCustomer will create new customer and select the default template from General ledger Setup table.
The Web Services series was started almost a year ago, after NAV Techdays 2015. All demos that I demonstrated have now been published. But I promised an extra example: call NAV OData web services directly from C/AL code. And at Directions EMEA 2016, a few weeks ago, I demonstrated that it is possible to call NAV OData web services from C/AL, without any custom dll, using .Net Framework library.