DIGITALL - Microsoft BizApps Guidelines¶
Welcome to the DIGITALL guard rails for the Microsoft Power Platform.
Draft
Since we have completely revised this documentation and many sections are brand new, we ask for your understanding if there are still minor errors or omissions. Please feel free to create issues on github.com at any time to bring them to our attention.
This is a constantly growing framework for our projects, the systems we operate, and the experience and approaches we have built up along the way. Its core audiences are the two roles working side by side on the same Dataverse environment:
- Customizers — makers configuring tables, forms, processes, and other low-code assets.
- Developers — engineers writing plugins, Custom APIs, web resources, and PCF controls.
It equally serves the architects who set the structure those two work within, and the project leads, analysts, and testers who scope and validate the work — the Where to start table points each role to its entry point.
These are the minimum standards for new projects. Deviations are permitted, but they must be documented and justified in the project's architectural documentation. See Scope & Principles for how that works in practice.
Contributing
Found something outdated, missing, or wrong? You can internally raise it in the MS BizApps Tech circle, open a GitHub issue, or send a pull request directly. See Governance & Contribution.
Where to start¶
Pick the entry point for your perspective:
| Perspective | Start here |
|---|---|
| New to a project (any role) | Setup & Onboarding, then the Quickstart |
| Customizer — tables, forms, processes, low-code | Customizing |
| Developer — plugins, Custom APIs, web resources, PCF | Coding + the Quickstart |
| Architect — solution, environment & deployment design | Architecture + Foundation |
| Project lead / analyst / tester — scope, process, quality gates | Foundation + Definition of Ready / Done |
| Looking for a command or template | Reference |
Our tooling¶
Several chapters of this guideline build directly on tooling maintained by DIGITALL:
- dgt.power (
dgtp) — CLI for code generation, assembly/package push, solution maintenance, and Dataverse data export/import. - Digitall.Plugins — base classes and abstractions for plugins, Custom APIs, and workflow assemblies.
- Digitall.Plugins.Registration — attributes for declarative, automated step registration.
- Digitall.Dataverse.Testing —
in-memory
IOrganizationServicefor fast, deterministic plugin unit tests.
Our Carrier/Workbench solution model is documented separately in Solution Concept.