domains / families / software-engineering / pcf

pcf

separate

Builds, tests, diagnoses, upgrades, deploys and verifies Power Apps component framework (PCF) code components for model-driven apps and Power Pages — field and dataset controls, standard and virtual (React) — from Microsoft-maintained templates and recipes pinned to a tested version matrix. Runs quality gates (manifest and host lint, source checks, lint, unit tests, production build), deploys with pac pcf push, verifies registration and form bindings, and guides Power Pages enablement, with guided setup for canvas apps. Use when the user wants to build, fix, upgrade, deploy or check a PCF control or code component, or asks why one fails to build, import, update or render. For a whole page use /model-apps:genpage; for a whole app use /model-apps:app-builder.

When to use

• Build PCF code components
• Fix PCF controls
• Upgrade PCF controls
• Deploy PCF controls
• Bind PCF controls
• Verify PCF controls
• Inventory PCF controls
• Diagnose PCF build or render failures

When not to use

• Whole custom page generation
• Whole model-driven app building
• Using existing controls without code changes
• Dataset controls on Power Pages

Skill page

Source