Skip to main content

Microsoft Dynamics NAV 2016 - How to Use Trigger Events - Part 2

Hi All,

Let's start it from where we left in Last Post.

Recap - "We Created A Custom Table & Page, Linked that to Standard Item Page. Then we Created a Custom Codeunit, Created a Function in Codeunit which Subscribe the OnBeforeDelete Event of Item Table and Called Custom Code in the Subscriber Function."

If you are missing the Story, Refer Table of Index.

In this article we will try to bring the Value of Last Revision for Item When Item Get Selected in Sales Line Using Trigger Event Subscription.

JUST TO CLARIFY - "Some people are getting confused on the new approach of customization using Events. They Feel that everything will be 100% out of standard Code. It's not True. Field Addition and Event Definition are still need to be done on Base Objects."

So let's Continue. Create a Field "Latest Revision No." in Sales Line Table and in Sales Order Subform Page.

Now We Need to Fill Revision No., Whenever there is a New Sales Line of Type Item is Added or Modified. Let's see how we used to do this till date.

Let's See how we Should We Do it Now - 

1. Create a New Function (CustomerAfterItemValidate) in Custom Codeunit 60000 Say MyCustomer Event Subscribers.
 > Navigate to Properties of Function and set as below -
   > Event - Subscriber
   > EventPublisherObject - Table 37
   > EventFunction - OnAfterValidateEvent (Say Yes to Confirmation Window).
   > EventPublisherElement - No.

2. Let's Add Same Code but as its a Different Object we need to Add some more conditions on the Event Subscriber as shown Below -

3. So That's it, we can test the Process with a Simple Example as shown below the Demo Steps -

Select a Item in Sales Order having Revisions Filled In Like 1000 & Latest Revision No. Should be Filled in Automatically as shown Below.

So With This Demo I hope we understand How to Use Trigger Based Events.

I Know a Common Question that most of you will have is  "Hey Saurav, What about the Code that I Write in the Mid of The Say OnValidate Trigger of the Field in any table. I am sure we cannot right it on Before or After. How we handle those?"

Hey Readers We will cover that also in the series, so stay connected and Provide your Feedback..

If you have any question / Suggestion / Feedback feel free to put as a comment to article or send me a Email using Contact Form.

If required you can download the Related Objects from SKYDRIVE.

File Name - Microsoft Dynamics NAV 2016 - Event Demo (Part 2 Objects).rar

Stay Connected, More is about to be Published. In Next Article we will see the Business & Integration Events.

Saurav Dhyani


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.