Book Image

Extending Microsoft Power Apps with Power Apps Component Framework

By : Danish Naglekar
Book Image

Extending Microsoft Power Apps with Power Apps Component Framework

By: Danish Naglekar

Overview of this book

Power Apps Component Framework is used by professional developers to extend the capabilities of model-driven and canvas apps. Extending Microsoft Power Apps with Power Apps Component Framework will take you through the basic as well as advanced topics using practical examples. The book starts by helping you understand the fundamentals of the framework, its lifecycle, and the tools that you'll use to build code components using best practices and file management guidelines. You'll then learn how to extend Power Apps step by step and apply the principles and concepts covered in the book to build code components for field type attributes. The book covers different ways of debugging code components and guides you through the process of building code components for datasets. You'll also explore the functions and methods provided by the framework to enhance your controls using powerful sets of libraries and extensions. As you advance, you'll get to grips with creating and managing authentication profiles, discover different ways of deploying code components, and configure code components in model-driven and canvas apps. Finally, you'll learn some of the important features of the framework and learn modern web development practices. By the end of this Power Apps book, you'll be able to build, debug, enrich, and deploy code components confidently.
Table of Contents (18 chapters)
1
Section 1: Fundamentals of the Power Apps Component Framework
6
Section 2: Building and Managing Code Components
12
Section 3: Enhancing Code Components and Your Development Experience

Understanding the ControlManifest file

ControlManifest is the metadata XML file that defines a component. It describes the namespace and name of the component, along with some additional information such as the kind of data it can configure (field or dataset), any additional properties that can be configured, a list of resource files that the component needs, and features the component supports.

The file has the following structure:

Figure 4.8 – Structure of ControlManifest file

Figure 4.8 – Structure of ControlManifest file

manifest is the root node of the XML manifest file. It has no additional attributes. control is the parent node for all the other nodes in the manifest file. It contains the following attributes:

  • namespace: The namespace of the control that shows up when a control is built (required).
  • constructor: This is the name of your control and the name of the constructor that initializes your component (required).
  • preview-image: The image that is used when configuring...