Skip to main content

Microsoft Dynamics NAV 2018 - API Part 4 - Develop Custom API.

Hi Readers,

We already have two posts about NAV 2018 API listed below -


API Part 1

API Part 2 - Configure API

API Part 3 - Consuming API


In this article, we will see how we can create a new custom API. We will customize NAV and see how API can be developed if we want to create a custom API's.



If you are interested in the small demo then please go further otherwise, I am sure you know how to consume these APIs.

Let's create a New custom table that we will use for API named as "External Items", with a boolean flowfield & Inventory Flowfield that will be set based on data entered from external systems in this table.

As in standard API Tables discussed in the earlier article, we will add Id Field with Field No. 8000



Now let's create a list page to see data in this page that is inserted by the external system.



Let's create an API page that we will require to configure in API Page which has all 44 standard pages published.

1. A New Page Type is added in NAV 2018 that is API.
2. Specify EntityName and EntitySetName that will be used in URL to access by the external system.
3. Also Speicy OdataKeyField the GUID Field i.e ID as shown below.



In the next article, we will discuss how we can add this new API to the external system. Let me know if any questions or suggestions.

Regards,
Saurav Dhyani

Comments

  1. Hi Saurav,

    Is there any article you would publish for "NAV 2018 - Develop Custom API"

    if yes then please share details about it.

    Thank you

    ReplyDelete
  2. Hi Saurav, can you please let me know the URL with passing company name as a parameter in query string, I tried many times , but all in vain , can you please help me with this

    ReplyDelete
    Replies
    1. @Vikas -
      Didn't get your question. Could you please explain.

      Delete
  3. Hi Saurav,

    Nice article. I am trying to search for your next article for this article but not getting any link on google. Tried to search with "Microsoft Dynamics NAV 2018 - API Part 5 - Develop Custom API".

    Please provide link of it.

    ReplyDelete

Post a Comment

Popular posts from this blog

VIEW SERVER STATE permission on SQL Server?

Hi all, Sometime While trying to Login into a database we face an error message as shown below. --------------------------- Microsoft Dynamics NAV Classic --------------------------- You cannot start Microsoft Dynamics NAV Classic because you do not have the VIEW SERVER STATE permission on SQL Server. Contact your system administrator. --------------------------- OK    ---------------------------

RTC Report It is not possible to instantiate the Visual Studio bridge.

Hi all, As a Navision developers I have Multiple Versions of Navision running in single Machine. As discussed Earlier in the post how to run multiple Version of RTC in single machine. So my machine have following details for RTC Versions - NAV 2009 R2    - is installed. NAV 2009 SP1  - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 SP1 IN\ NAV 2009         - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 IN\ This approach has been working great for execution of Classic and RTC Clients. However, after installing Dynamics NAV 2009 R2, if i tried to view the Layout for an NAV 2009 SP1 Report i was getting the following error: ---------------------------  Microsoft Dynamics NAV Classic  ---------------------------  It is not possible to instantiate  the Visual Studio bridge.  ---------------------------  OK    --------------------------- After searching for the error i figured out the issue was due to - Design change in NA

NAV 2013 R2 - Cumulative update 12 Released.

Hi all, Please find below the details of  Cumulative Update 12 released for Microsoft Dynamics NAV 2013 R2. Title - Cumulative Update 12 for Microsoft Dynamics NAV 2013 R2 Build No. - 38053 Release Date - October, 2014 Local Version Included - AU, AT, BE, CH, DE, DK, ES, FI, FR, IS, IT, NA, NL, NO, NZ, SE, UK, RU Download Link Note: Implementing this cumulative update will require a database conversion unless you have already implemented update rollup 5.