Manifest schema reference

[This topic is pre-release documentation and is subject to change.]

This section contains reference documentation for manifest schema generated using the PowerApps CLI.

Important

The Available for tab shows which elements are supported by model-driven apps and canvas apps (experimental preview). It is recommended to check the Available for section for each individual property whether it is supported or not. For example, the code element is supported for both model-driven apps and canvas apps, but html and img properties in code elements doesn't support canvas apps.

Element Description Available for
code Refers to the path where the resource files are located. Model-driven apps and canvas apps (experimental preview)
control Defines the component's namespace, version and display information. Model-driven apps and canvas apps (experimental preview)
css CSS describes how code components are to be displayed on UI. Model-driven apps and canvas apps (experimental preview)
data-set The data-set node in the component manifest represents a specific, configurable representation of a set of entity records. Model-driven apps
html Use HTML webresources to create user interface elements for client extensions. Model-driven apps
img The img webresource allows you to add images for the code components. Model-driven apps
manifest Manifest is the metadata file that defines a component. It is an XML document that describes
- The namespace 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.
- One of them must be a JavaScript web resource. This JavaScript must include a function that will instantiate an object. This implements an interface that exposes methods that are required for the component to work. This is called the component implementation library.
- The name of a JavaScript function in the component implementation library that will return an object that applies the required interface.
When someone configures a component in the application, the data in the manifest filters out the available components so that only valid components 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 control can specify values. These property values are then available to your component function at run time.
Model-driven apps and canvas apps (experimental preview)
property The property node defines a specific, configurable piece of data that the component expects from the Common Data Service. Model-driven apps and canvas apps (experimental preview)
property-set Defines an inner configuration within a data-set manifest node to allow you to explicitly configure a column of your data-set against an attribute of a given type from the entity against which the data-set is configured Model-driven apps
resources The resources node in the component manifest refers to the resource file that components require to implement it's visualization. Model-driven apps and canvas apps (experimental preview)
resx The resx webresource is used to manage the localized strings you define. Model-driven apps and canvas apps (experimental preview)
type-group The type-group node defines a set of types identified by a single name. This information can be used to identify the data types supported by a specific property. Model-driven apps and canvas apps (experimental preview)
feature-usage The feature-usage element acts as a wrapper around the uses-feature elements, which themselves allow developers to declare which features their component wants to use. If there are no uses-feature elements defined, the feature-usage element is not required. Model-driven apps

PowerApps component framework Manifest Schema Reference
PowerApps component framework API Reference
PowerApps component framework Overview