How tinestaric/bcexamples works
Project type and purpose
• This repository (“BCExamples”) is a collection of Microsoft Dynamics 365 Business Central (BC) AL-based extension samples. Each top-level folder (e.g. CallApiWithUserPool, ScheduleJobsAsS2S, SecureEndpoints, etc.) is a standalone AL extension demonstrating a particular BC feature or integration (OAuth2, job scheduling, custom API pages, event subscribers, formula parsing, etc.).
• The README simply labels the repo “BCExamples,” confirming it’s a set of illustrative modules rather than a single monolithic application.
File structure
• Top-level directories:
• CallApiWithUserPool, InsertLockTimeouts, PreprocessingSymbolCleanup (PowerShell script), ScheduleJobsAsS2S, SecureEndpoints, StringFormulaCalculator, TriggerLogger.
• Each AL project has an app.json, .al code files under /src or root, and in some cases PermissionSets.
• Patterns & architectural hints:
• “src/API” folders ⇒ custom API pages/codeunits.
• “JobQueue” folder ⇒ use of BC’s job queue.
• OAuth2 and TokenGetter subfolders ⇒ pluggable authentication providers.
• TriggerLogger uses subscriber codeunits to log database changes (event-driven pattern).
• Build/deploy artifacts:
• PowerShell scripts (PreprocessingSymbolCleanup.ps1, BCPTRunner.ps1) ⇒ automation of symbol cleanup or BC container deployment.
• .csproj and .cs files in CallApiWithUserPool ⇒ a small C# console app invoking BC web services using a user pool.
Detail without over-splitting
• Inside each, list primary object types (e.g. Codeunits, Pages, Tables, Interfaces) only if space allows
• Patterns: event subscriptions, interface-based providers, job queue scheduling
• Keep the focus on how code travels from developer machine to BC runtime, and how BC interacts internally (DB, subscribers, job queue) and externally (OAuth2, REST).