apptest-onbeforecompanyopen.md

title	description	author	ms.date	ms.topic	ms.custom	ms.author	ms.reviewer
Replacing OnBeforeCompanyOpen and OnAfterCompanyOpen	Describes how to replace OnBeforeCompanyOpen and OnAfterCompanyOpen events.	SusanneWindfeldPedersen	05/01/2024	conceptual	evergreen	freddyk	jswymer

Replacing OnBeforeCompanyOpen and OnAfterCompanyOpen

To improve the login time for [!INCLUDE prod_short], extensions should no longer use the OnBeforeCompanyOpen and OnAfterCompanyOpen events. Following are some recommended patterns to use in place of these events.

• Move the code to the actual usage of the extension.

• Code written on the subscribers that are called from these triggers must be safe. Every Get, Modify, Delete, and Insert operation must be written with if...then, to avoid raising conditions that could prevent user from signing in.

• The code should start with a check if not guiallowed then exit; to avoid impacting Web services code. Other checks to exit early should be added to the beginning of the code so that login performance isn't affected.

• If the extension is subscribing to OnBeforeCompanyOpen or OnAfterCompanyOpen triggers in order to perform some long-running data update, then either call Update when the extension gets called in code for the first time or apply the new task scheduler pattern for Update 6 and later. This applies to code that is not crucial.

  // Add 15s
  TaskScheduler.CreateTask(Codeunit::"Job Queue User Handler",0,true,CompanyName,CurrentDateTime + 15000);

• If you're inserting data for a newly created company, we recommend subscribing to OnCompanyInitialize from Codeunit 2 instead. Use Installation or Upgrade code for the extension, or to set up on the first usage and if this isn't possible only then OnCompanyInitialize should be used to populate data for new companies, since this runs after every upgrade.

See also

Checklist for submitting your app
Rules and guidelines for AL code