Publishing your own event means in a scenario where you are not able to find standard events , you can also define your event and publish it for use.
For Example:
In Job Journal Line page you have no event in posting date field.
Publishing your own event means in a scenario where you are not able to find standard events , you can also define your event and publish it for use.
For Example:
In Job Journal Line page you have no event in posting date field.
EventSubscribers are a nice feature to add code to triggers in standard objects. It’s the replacement for changing the code directly in standard objects.
A core part of extension-based “customization” is the use of events and event subscribers.
To identify an event and generate an event subscriber code template, we added the Event Recorder in the client some time ago, allowing recording and inspecting of thrown events; however, in many cases, developers are either aware of the event they want to subscribe to or want to have a fast way to search for the event (with type ahead/completion) and then insert event subscriber in code context.
Feature details
Use the new Shift+Alt+E shortcut in the AL code editor to invoke a list of all events.
A core part of extension-based “customization” is the use of events and event subscribers.
To identify an event and generate an event subscriber code template, we added the Event Recorder in the client some time ago, allowing recording and inspecting of thrown events; however, in many cases, developers are either aware of the event they want to subscribe to or want to have a fast way to search for the event (with type ahead/completion) and then insert event subscriber in code context.
Feature details
Use the new Shift+Alt+E shortcut in the AL code editor to invoke a list of all events.
I’ve written a lot in the past about handling breaking schema changes on extensions and the best practice to use the ObsoleteState object property to signal to your developers or third-party ISV users of your extensions that you’re planning to remove something in your codebase.
It is possible to substitute reports from the base application with “custom reports“. Great!
This can be done by subscribing to the “OnAfterSubstituteReport” event published by “Codeunit 44 – ReportManagement“.
Source : Roberto Stefanetti NAV & Business Central Blog
Read more…
Eventing is major part while upgrading to business central, we face alot of customisation done in Customer database which needs to be evented and converted into extension.