Skip to main content

Release Plan — May 2026

Business Central 2026 Wave 1 — CU1 Aligned with Business Central cumulative update v28.1

Overview​

This release plan tracks proposed AL Copilot Skills for the May 2026 contribution cycle.

Contributors: add your skill proposal below using the entry template. Once approved via Pull Request by the repository maintainer, begin development and submit the completed skill to main through a separate Pull Request.

Proposed Skills​

bc-isolated-storage-generator​

FieldDetails
Skill Namebc-isolated-storage-generator
Short DescriptionGenerates secure isolated storage patterns for Business Central extensions, including encryption/decryption helpers, secret management, and credential storage implementations following Microsoft security best practices.
Target BC Version (optional)28.1
Status🔵 In Development

Author​

Co-Authors (optional)​

Motivation​

Many AL extensions require secure storage of sensitive data like API keys, authentication tokens, connection strings, and user credentials. Business Central provides the Isolated Storage API for this purpose, but implementing it correctly with proper encryption, error handling, and secret rotation can be complex. This skill provides tested patterns and templates for secure credential management, helping developers implement security best practices without reinventing the wheel for each project.

bc-approval-workflow-generator​

FieldDetails
Skill Namebc-approval-workflow-generator
Short DescriptionGenerates complete approval workflow implementation for custom tables in Business Central, including workflow templates, event subscriptions, approval entries integration, user setup validation, approval actions on pages, notification handling, and delegation logic following standard BC approval patterns.
Target BC Version (optional)28.1
Status🔵 In Development

Author​

Co-Authors (optional)​

Motivation​

Custom document tables (like custom purchase requisitions, expense reports, or custom orders) often require multi-level approval workflows similar to standard BC documents. Implementing approval workflows from scratch involves complex integration with BC's Approval Management system, including workflow templates, event conditions, responses, approval user setup, delegation, notification handling, and record status management. This skill automates the generation of all necessary objects following Microsoft's approval workflow architecture, enabling developers to quickly add enterprise-grade approval capabilities to custom tables without deep expertise in the approval framework internals.

skill-contribution-assistant​

FieldDetails
Skill Nameskill-contribution-assistant
Short DescriptionGuides contributors to design, refine, and submit high-quality skills for AL Copilot Skill Collection, including onboarding questions, non-intrusive opportunity detection, quality gates, and PR-readiness checks.
Target BC Version (optional)28.1
Status✅ Merged

Author​

Co-Authors (optional)​

Motivation​

The collection can scale faster if contributors receive a practical assistant that converts real user needs into reusable, review-ready skills. This skill reduces rework by standardizing onboarding, scope framing, anonymization, repository compliance, and release-plan integration.

onprem-remote-deploy​

FieldDetails
Skill Nameonprem-remote-deploy
Short DescriptionDeploys AL apps to remote Business Central OnPrem servers from VS Code using WinRM, SSH, SMB, or RDP tsclient-pull strategies with fallback guidance for restricted networks.
Target BC Version (optional)28.1
Status✅ Merged

Author​

Co-Authors (optional)​

Many projects need repeatable AL deployment automation to on-premises Business Central servers where direct connectivity is partially or fully blocked. This skill provides a practical decision matrix and implementation patterns so teams can deploy reliably across different network/security constraints.

bc-reports​

Skill Namebc-reports
Short DescriptionStandards and guardrails for authoring Business Central reports in AL and RDLC. Covers report object structure, DataItem hierarchy, RDLC sizing, SetData/GetData index management, body width validation, and rendering best practices.
Target BC Version (optional)28.1
Status✅ Merged

Author​

Co-Authors (optional)​

Motivation​

AL report objects and RDLC layouts have many subtle requirements (DataItemLink, SetData index order, body width constraints, PageHeader/Footer sizing) that are easy to get wrong and hard to debug. This skill enforces correct patterns before code reaches review, reducing rework and rendering failures.

bc-field-propagation​

Skill Namebc-field-propagation
Short DescriptionPropagates custom fields from source documents and journal lines to posted documents, archived documents, and ledger entries. Selects Pattern A (TransferFields - zero code) or Pattern B (EventSubscriber with dedicated codeunit per module) based on whether the posting codeunit uses TransferFields.
Target BC Version (optional)28.1
Status✅ Merged

Author​

Co-Authors (optional)​

Motivation​

Custom fields added to Sales, Purchase, Transfer, or journal source tables often need to propagate to all posted documents, archive copies, and ledger entries. Getting the pattern wrong - using a manual EventSubscriber when TransferFields already covers the field, or using different Field IDs on source and target - causes data inconsistency and maintenance debt. This skill enforces the correct pattern based on how the BC posting codeunit works, and provides a complete event catalog for all major posting chains.

{skill-folder-name}​

FieldDetails
Skill Name{skill-folder-name}
Short Description{One-to-two sentence description of what the skill does}
Target BC Version (optional){BC Version}.{CU Number}
Status🟡 Proposed · 🟢 Approved · 🔵 In Development · ✅ Merged

Author​

Co-Authors (optional)​

Motivation​

{Brief explanation of why this skill is needed and what problem it solves}

Contribution Workflow​

  1. Fork the repository and create a branch from main.
  2. Add your skill entry to the corresponding monthly plan file.
  3. Open a Pull Request targeting main for plan approval.
  4. Wait for approval from the repository maintainer (@fernandoartalf).
  5. Develop the skill following the skill creation instructions.
  6. Submit the completed skill via a new Pull Request targeting main.

Summary​

SkillAuthorStatus
bc-isolated-storage-generator@fernandoartalf🔵 In Development
bc-approval-workflow-generator@fernandoartalf🔵 In Development
skill-contribution-assistant@AlexP0lo✅ Merged
onprem-remote-deploy@AlexP0lo✅ Merged
bc-reports@cperezsx✅ Merged