Skip to main content

Microsoft Dynamics NAV 2016 - What is Events & Subscriptions

Hi All,

As Promised in Earlier Article Let's Start with Understanding Events and subscription In a Simple Manner.

Let's Start with a Simple Example what an Event & Subscriber are in Microsoft Dynamics NAV.

As most of all use Facebook let's take that as Example to understand it -




1. We have a page in Facebook related to Blog Article. Whenever there is a New Article Posted on Blog, it get automatically update on Page. ((EVENT))

2. If readers like the articles published in my Blog, they Like the Page to get updates whenever published. ((Readers Subscribe Page))

3. Now Subscriber (Reader on Facebook) can take action based on his/her wish -
   a) He/She can comment on the Event that occurred.
   b) He/She can ignore the Event that occurred.
   c) He/She can Share the Event that occurred.
   d) He/She can Read the article, the Event that occurred.

When a Article get published on the Facebook Page, an Event Occur and Look for All Subscribers and notify them about event. Now Subscriber can do different things as discussed in above example.

Below is the summary what we discussed.


Now Let's see Same Thing In Navision -

When I as a user post a Item From Sales Order it follows a Business process as shown below -



Wherever you see a Green Start that means we used to Place Customize Code on all those Places, as per business requirement. It can be on -
> Table Fields Triggers.
> Table Triggers.
> Codeunit Functions.
> Page Field Triggers & Page Actions.

With Events and Subscription Microsoft Is suggesting to keep all these code in a seprate place and with Events & Subscription Microsoft Provides a Capability to call that customize code that you have during standard Business Process.

In Future Post we will see More About Events and Subscription.

Hope the Idea is Clear about same, Now in Next articles on this series we will see different types of Events in Microsoft Dynamics NAV 2016.

Stay Connected and Keep Reading.

Thanks & Regard,
Saurav Dhyani
saurav-nav.blogspot.com

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.