Integration Events in Microsoft Dynamics NAV 2016

Microsoft Dynamics NAV 2016 introduces a new type of integration point: events.

Events are a C/AL feature in which an object maintains a list of its subscribers, and notifies them automatically of any state changes. This is done by calling on a subscriber method. Subscriber methods don’t need to be in the same object and this fact enables integration developers to build decoupled systems. You can write Microsoft Dynamics NAV solutions by interfering with and rewriting much less of the base application code.

In addition to enabling you to define your own events, the Microsoft Dynamics NAV application comes with a set of events in different areas of the product. You can see the list of events on the Get Started with Eventing page in the Dynamics NAV Developer Center.

For more information, see Introducing Events.

As we continue our innovation, we would like to get your feedback and suggestions for future integration events. In order to manage the process and be able to make the right decisions and implementation, we kindly ask you to follow the process below:

  1. Go to the MS Connect Product Suggestions site for Dynamics NAV at
  2. Log in, and then fill this template:
    1. Title:   [IntEvent] Event Name.
      For example: [IntEvent] OnAfterReleaseSalesOrder
    2. Product Area:  Integration Events
    3. In the Description field, please provide the following information:
      1. Which business scenario do you want to solve?
      2. Where do you want the event placed?
  3. Signature of the event (meaning function name with parameters)?
  4. Are there other events needed to solve your business scenario?
  5. Which other options do you have if this event is not implemented?
  6. Have you tried to implemented this event yourself to verify it works for your business scenario?
    1. Did you try on an existing release of Dynamics NAV?
    2. If yes: were you able to make it work?
    3. If not, why?

Microsoft and the Dynamics NAV team do not make any commitment about the implementation of the requested events or the timeframe when this could happen. Your input will be handled as suggestions to the product teams and be evaluated against other product suggestions and feature improvements.  Please note that suggestions are covered by the Connect terms of use which can be found at

Comments (10)

  1. Vincent Vancalbergh says:

    Events are great and hold a lot of potential. I have been waiting for an OnAfterInsert event since forever 🙂
    A future improvement though would be to also publish events for field validates and Codeunit functions being called.

  2. Happy New Year everyone!
    We’re still looking for more suggestions so go ahead like Vincent and post in comments or use the Connect links in the blog and post your suggestions.
    Good suggestions will be implemented and are likely to be released in CU updates so go ahead and make your suggestions.

  3. Hi, I am using Windows 10 Enterprise. when i run Nav 2016 development environment, its locked. i am able to modify objects using old editor only. Any suggestion ?

  4. Theo Stock says:

    We are experiencing situations where Events stop “Firing”, so Workflows and other Integration Event Subscibers stop executing. After a NAV Server Restart operation come back to normal, but Workflows and other Records are in an undefined stated as the events that were supposed to update them had not executed.

    Has anybody else experienced this very disturbing situation?

    Thanks Theo

  5. Chin says:

    How if we have customize the codes (added some codes) in the Events in previous version, where else can we put the customized codes when upgrade to NAV 2016?

  6. Ashley McINtyre says:

    I am also having events that stop firing, with no error message and still enabled, however when I re-compile the object (even with no code changes) they start working again!! Scary.

    1. So, with more than one reply about events going awry we thought we’d better reply.
      I’ve checked with our support and engineering groups and so far we haven’t received any similar reports of bugs. That doesn’t mean it doesn’t happen, it just means we don’t have an easy solution yet.
      As you can imagine, with the data below, it’s hard to work out what’s really gone wrong, so if you can help us with more description, that would be great.
      For example
      1) can you regularly reproduce the error?
      2) is it occurring with the out-of-the-box workflow templates or with custom workflows?
      3) do you think you can write a simple codeunit/event sample that shows the error?
      4) does it always seem to fail on the same spot or are the events that fail more random?
      If you have more details, please write me
      Thanks and good luck,

      1. Antonio Checa says:

        Hi Stuart, any feedback on the issue?
        The problem having this workflow events going down without any notice is big…
        All sales orders get stuck and we have to do a really dirty job inside so water flow again…
        I posted and issue detailing workflow log and where it got stuck.,d.d24

  7. To anyone who might experience the issue with events not working:

    We noticed that the error occurs after you have modified and saved the Purchase Line table. Re-compiling the Codeunit with your events will fix the issue.

Skip to main content