bc-install-codeunit-generator

Generate Business Central extension install codeunits with idempotent triggers and version checks.

20|5|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/fernandoartalf/AL-Copilot-Skills-Collection --skill bc-install-codeunit-generator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bc-install-codeunit-generator
Source: https://github.com/fernandoartalf/AL-Copilot-Skills-Collection/tree/main/skills/bc-install-codeunit-generator
Command: npx skills add https://github.com/fernandoartalf/AL-Copilot-Skills-Collection --skill bc-install-codeunit-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines the generation of robust install codeunits for Business Central extensions, ensuring proper handling of first install, reinstall, data seeding, and telemetry logging.

Core Features & Use Cases

  • Generate Install Codeunits: Produces ready-to-use codeunits with correct triggers and idempotent data initialization.
  • Handle Reinstall Scenarios: Differentiates between first-time install and reinstall using version checks and manages data patches.
  • Use Case: A developer needs to implement a standardized install procedure for a new extension, including default data setup, optional telemetry, and reinstall patching, all automatically generated.

Quick Start

Use the bc-install-codeunit-generator skill to create a comprehensive install codeunit that detects a fresh install, initializes default data, and logs telemetry events.

Frequently Asked Questions about bc-install-codeunit-generator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Business Central install codeunit that handles reinstall and data seeding?

To create a Business Central install codeunit, use automated generation to produce triggers for first install, reinstall, data seeding, and telemetry. This ensures idempotent data initialization and proper version checks across multiple deployment scenarios without manual coding.

What is the difference between first install and reinstall triggers in AL development?

In AL development, first install triggers run on initial extension deployment, while reinstall triggers execute on subsequent reinstalls. Automated install codeunit generation differentiates these scenarios using version checks to apply data patches correctly and prevent duplicate records.

How do I ensure idempotency when seeding default data in a Business Central extension?

To ensure idempotency when seeding default data in a Business Central extension, implement version checks within your install codeunit triggers. Automated code generation provides base patterns that prevent duplicate data initialization across multiple install or reinstall scenarios.

Can I add telemetry logging to my Business Central install codeunit?

Yes, you can add telemetry logging to your Business Central install codeunit. The automated generator includes optional telemetry logging capabilities within the install triggers, allowing you to track extension setup events and data patching operations consistently.

What is the best way to automate extension setup procedures for Business Central?

The best way to automate extension setup procedures for Business Central is generating a standardized install codeunit. This approach handles default data setup, reinstall patching, and telemetry logging automatically, ensuring consistent deployment across environments.