Skip to main content

Unleashing the Potential of Bound API Actions in MS Dynamics 365 Business Central.

 Hi Readers,

In continuation to the API Series today we will discuss about Unleashing the Potential of Bound API Actions in MS Dynamics 365 Business Central.

  • This video is about bounded actions in Dynamics 365 Business Central APIs. 
  • Bounded actions are a type of API action that allow you to perform specific actions on a particular data entity. For example, you can use a bounded action to create a sales order, post a sales order, or ship and invoice a sales order.
  • To use a bounded action, you first need to get the ID of the record you want to perform the action on. 
  • Then, you can use the POST HTTP method to call the bounded action. The URL for the POST request should include the ID of the record and the name of the bounded action.
  • The video provides several examples of how to use bounded actions. Example, the speaker shows how to convert a sales quote to a sales order and then how to ship and invoice the sales order.

Overall, this video is a good introduction to bounded actions in Dynamics 365 Business Central APIs. The speaker provides clear explanations and examples, and the video is easy to follow.



Comments

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.