Singleton on AL Guidelineshttps://alguidelines.dev/navpatterns/1-patterns/singleton/Recent content in Singleton on AL GuidelinesHugo -- gohugo.ioen-usSingleton Tablehttps://alguidelines.dev/navpatterns/1-patterns/singleton/singleton-table/Mon, 01 Jan 0001 00:00:00 +0000https://alguidelines.dev/navpatterns/1-patterns/singleton/singleton-table/Singleton Table By Elly Nkya at Microsoft Development Center Copenhagen _ _ Problem: The developer needs to define a single record that can contain a set of rules and behavior (optional, mandatory, or defaulting mechanisms), that apply to a functionality, and can be configured by a user. Forces You want a central place to define the address and logo of your company (see Company Information table). You want to define the no.Singleton Codeunithttps://alguidelines.dev/navpatterns/1-patterns/singleton/singleton-codeunit/Mon, 01 Jan 0001 00:00:00 +0000https://alguidelines.dev/navpatterns/1-patterns/singleton/singleton-codeunit/By Bogdana Botez at Microsoft Development Center Copenhagen Problem: In some situations, global state needs to be preserved at runtime throughout a session. There are functionality areas in NAV where centralized application management code is needed, like for example managing permissions, notifications, the debugger etc. State needs to be preserved across calls to the management codeunit. For example: The debugger needs to remember the session which is being debugged The permission manager has a testability function, where it can be set to emulate that it’s running as a SaaS (Software As A Service – the cloud) platform, even when the tests run in a “on-premise” local lab.