12
Getting the subscriber procedure parameters correct is required to make eventing work but there is little to guarantee its correctly defined.
It would be great if the environment could warn us that the publisher and subscriber params don't match.
Moreover providing something in the code to show the sender object would also help. Example below.
Below I've included an example from the Manual setup publisher.
//**** current ****//
/// The subscriber should call the methods on the Sender object.
[IntegrationEvent(true, false)]
internal procedure OnRegisterManualSetup();
begin
end;
//**** current ****//
//**** proposed ****//
/// The subscriber should call the methods on the Sender object.
///
[IntegrationEvent(true, false)]
internal procedure OnRegisterManualSetup(var Sender Codeunit:"Manual Setup");
begin
end;
//**** proposed ****//
It would be great if the environment could warn us that the publisher and subscriber params don't match.
Moreover providing something in the code to show the sender object would also help. Example below.
Below I've included an example from the Manual setup publisher.
//**** current ****//
/// The subscriber should call the methods on the Sender object.
[IntegrationEvent(true, false)]
internal procedure OnRegisterManualSetup();
begin
end;
//**** current ****//
//**** proposed ****//
/// The subscriber should call the methods on the Sender object.
///
[IntegrationEvent(true, false)]
internal procedure OnRegisterManualSetup(var Sender Codeunit:"Manual Setup");
begin
end;
//**** proposed ****//
STATUS DETAILS
Needs Votes

Business Central Team (administrator)
Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future.
Best regards,
Business Central Team