Use code components in portals (Preview)
[This article is pre-release documentation and is subject to change.]
Power Apps component framework empowers professional developers and app makers to create code components for model-driven and canvas apps (public preview) to provide enhanced user experience for the users to work with data on forms, views, and dashboards. More information: Power Apps component framework overview
Power Apps portals now supports controls for model-driven apps created using Power Apps component framework. To use code components in portals webpages, follow these steps:
After following these steps, your users can now interact with the code component using the portal page that has the respective basic form.
- This is a preview feature.
- Preview features aren’t meant for production use and may have restricted functionality. These features are available before an official release so that customers can get early access and provide feedback.
- Portals only supports code components that are added to a field in a model-driven app currently.
User must have a valid Power Apps license. More information: Power Apps component framework licensing
System Administrator privileges are required to enable the Power Apps component feature in the environment.
Your portal version must be 9.3.3.x or higher.
Your starter portal package must be 9.2.2103.x or higher.
Create and package code component
To learn about creating and packaging code components created using Power Apps component framework, go to Create your first component.
Supported field types and formats
Portals supports restricted field types and formats for using code components. The following table lists all supported field data types, and formats.
Floating Point Number
More information: Attributes list and descriptions
Unsupported code components in portals
Data-set components aren’t supported.
The following code component APIs aren’t supported:
uses-feature element must not be set to true.
Value elements not supported by Power Apps component framework.
Add a code component to a field in model-driven app
To learn about how to add code component to a field in model-driven app, go to Add a code component to a field.
Code components for portals are available for web browsers using the client option of Web.
Configure portal for code component
After the code component is added to a field in model-driven app, you can now configure portals to use the code component in the basic form. Once you configure the code component on an basic form, ensure you configure table permission to allow Read access to Web Resource table for the portal users before they can see the component on the portal page.
To add code component to an basic form:
Open Portal Management app.
On the left-pane, select Basic Forms.
Select the basic form you want to add the code component to.
Select Basic Form Metadata.
Select New Basic Form Metadata.
Select Type as Attribute.
Select Attribute Logical Unit Name.
For Control Style, select Code Component.
Save and close the form.
Allow Read access to Web Resource table
Portals requires Read permission to be set on Web Resource table before users can see the code component on the web page with the basic form.
To configure Read access on Web Resource table:
Open Portal Management app.
On the left-pane, select Table Permission.
Select Web Resource (webresource) for Table Name.
Select your website record.
Select Global for Scope.
In Privileges, select Read.
Under Web Roles section, select Add Existing Web Role.
Select the web role for the users that you want to see the code component in portals.
For example, Anonymous Users for anonymous users, Authenticated Users for users authenticated by portals, or a custom web role.
Select Save & Close.
Once you add the basic form to a web page, users assigned to the selected web role can now see the code component on the portal page having the selected basic form.