Skip to main content

Microsoft Dynamics NAV 2018 - API Part 2 - Configure API.

Hi readers,


In the first article, we discussed exploration of API released with Microsoft Dynamics NAV 2018.


As we knew from the last article we read the Microsoft document says that there are 44 API released in Base Microsoft NAV. Let's see how we can access that list and how to configure API.




To Start with Microsoft have added a page API Setup (5469) to initialize of update all APIS defined in NAV Objects.

Don't get confuse with data in this page, we need to focus on action Integrate API as shown below.



So what will happen if we click on it -

1. System will look for all subscriber of the Published Event "ApiSetup" in Codeunit Graph Mgt - General Tools.

2. For Every Subscriber if it is API then system will Add or Update Integration Records for API's.

Next step is to check APIs which are added or updated. As in previous article we see that Microsoft added a new virtual table in NAV 2018 - 2000000193 (Api Web Service). Lets create a list page based on this table and see the data inside this as shown below.



Now after finding information from MSDN to access any of these API's below is the format to access. http://<<Server Name>>:<<OData Port>>/<<Service Name>>/api/beta

In my case, it is - http://localhost:11048/DynamicsNAV110/api/beta

Lets try to access is and see results.

So what we are missing, after reading more about it we need to set following parameter in service.

1. Service Default Company. -- Company Name that will be used to get/post data from API's.
2. Enable API Services.     -- Enable API Service to get results from URL used above.
3. Enable ODATA Services.   -- Enable Odata as API depends on ODATA Services.
4. OData Base URL.          -- The public URL for accessing OData services.
5. Port.                    -- Will be used in the URL Above.


So lets try to access the base URL again and see a list of pulished API in Microsoft Dynamics NAV 2018. As highlighted 44 published API is displayed on the page.

Hope you find the information useful and will be able to configure API In your environment.

In Next article we will try to see demo of how we can use these standard API. That may not be the how we will actually use it but a simple demo and then i will leave it with everyone open mind to use it further.

Let me know your views.

Regards,
Saurav Dhyani

Comments

Popular posts from this blog

Welcome - Microsoft Dynamics 365!

Hi All, In this article we will discuss the new introduced member of Dynamics Family. Yes you heard it correctly, one more new member with Name "Microsoft Dynamics 365" . #ProjectMadeira   #Dynamics365

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.