What are custom components?
[This topic is pre-release documentation and is subject to change.]
Custom components are a type of solution component, which means they can be included in a solution and installed in different environments. More information: Package and distribute extensions using solutions.
You add custom components by including them in a solution and then importing it into the system. Once they are in the system, admin and system customizers can configure form fields, sub-grids, views, and dashboard sub-grids to use them in place of default component.
Custom components are comprised into three components:
- Component implementation library
Manifest is the metadata file that defines a component. It is an XML document that describes:
- The namespace and name of the component.
- The kind of data it can be configured, either a field or a data-set.
- Any properties that can be configured in the application when the component is added.
- A list of resource files that the component needs.
- The name of a TypeScript function in the component implementation library that will return an object that applies the required component interface.
When someone configures a component in the application, the data in the manifest filters out available component so that only valid component for the context are available for configuration. The properties defined in the manifest for a component are rendered as configuration fields so that the person configuring the component can specify values. These property values are then available to your component function at run time. More information: Manifest file reference
Component implementation library
Implementing the component library is one of the key step when you are developing custom components using PowerApps component framework. Developers can implement component library using TypeScript. Each custom component must have a library that includes the definition of a function which returns an object that implements the methods described in the custom component interface.
The object implements the following methods:
These methods controls the lifecycle of the custom component.
When the page loads, the application requires an object to work with. Using data from the manifest, the code gets the object by calling
var obj = new ["namespace on manifest"].["constructor on manifest"]();
If the namespace and constructor values from the manifest were
LinearInputControl respectively, the code to instantiate the object would be this:
var controlObj = new MyNameSpace.LinearInputControl();
When the page is ready, it initializes the component by calling the init function with a set of parameters.
|context||Contains all the information about how the component is configured and all the parameters that can be used within the component along with the framework APIs. For example, the
|notifyOutputChanged||Function that alerts the framework that the component has new outputs ready to be retrieved asynchronously.|
|state||Contains component data from the previous page load in the current session if component explicitly stored it earlier using
|container||An HTML div element to which you will append the HTML elements for the UI that defines your component. To display the value in the UI, you must get the data from
User changes data
After the page loads, your component is displaying the data until the user interacts with the component to change the data. When this occurs, you can manage it any way you like, but you must call the function passed in as notifyOutputChanged parameter in the init function. When you use this function, the platform will then respond by calling the getOutputs method that you must implement. The getOutputs methods will return any values that represent changes a user made. For a field component, this would typically be the new value for the component.
App changes data
If the data is changed by the platform it will call the updateView method of your component object and pass a new context object as a parameter. You must implement this method and use it to update the value displayed in the component.
When the user navigates away from the page the component will lose scope and usually all the memory allocated in that page for the objects in your component will be cleared. However, some items based on the browser implementation mechanism might stay and consume memory. Typically, these are event handlers. If user wants to store the information, they should implement the
setControlState method so that the information will be given next time within the same session.
You should define a destroy method in your object. This will be called when the page closes and you should use it to remove any clean up code such as removing any event handlers.
Each custom component should have a resource file to construct its visualization. You can define a resource file in the manifest. The resource node in the manifest file refers to the resources that component require to implement its visualization. More information: Resources