Comments
Strong support for this feature. The lack of a pre-InitReport trigger severely limits our ability to programmatically influence the request page — even for something as basic as loading user-specific filter presets.As a result, we’re forced into fragile workarounds (custom wrappers, extra launch pages, etc.), which feel unnecessary for what should be a clean solution.Adding OnBeforeInitReport() would allow developers to deliver personalized report experiences that persist across sessions and users, without needing to rewrite standard report workflows. This is a high-impact, low-footprint enhancement.
I naturally assumed this would be a feature introduced with the addition of interfaces.I too would like this feature, because interfaces are functionally a "CodeunitRef", so it makes perfect sense to need to bind event subscriptions for them, it would also represent a performance increase due to the toggling off of event subscribers for interface implementation codeunits.This feature's absence is extremely limiting.
This is really an issue when moving environments to another tenant. When you move a Business Central environment to a new tenant, the user records from the old tenant persist in the environment. These users don't have a BC license and cannot be deleted through the UI because they are no longer linked to Microsoft Entra ID (Azure AD). This creates clutter and confusion, especially in environments with many users.