Summary

Completed

In this module, you build a reusable code component with the Power Apps component framework. You move from lifecycle logic and manifest design through platform features, packaging, and deployment, ending with a maker-ready control on a Dataverse form.

What you learned

• A code component moves through four lifecycle methods: init, updateView, getOutputs, and destroy. Its manifest, ControlManifest.Input.xml, declares the bound and input properties or dataset that shape whether the component is a field or dataset component type.
• The context parameter connects your code to the manifest's declared properties through context.parameters, signals output changes with notifyOutputChanged, and exposes Device, Utility, and Web API features for supported hosts. Model-driven components declare those APIs in feature-usage, and canvas components that call external domains use external-service-usage, which can affect licensing.
• A test harness and pac pcf push validate a component during development. From there, you package it into a solution with pac solution init and pac solution add-reference, and build it as managed or unmanaged. Importing that solution into an environment lets a maker add the finished control to the right app surface without touching code.

Learn more

• Power Apps component framework overview
• Component framework manifest schema reference
• Component framework context object reference
• Power Platform CLI pcf command reference