sp-dev-fx-webparts/samples/react-enhanced-powerapps
Hugo Bernier c7fecfd583 Moved disclaimer to bottom 2021-11-07 02:11:17 -05:00
..
.tours Merge commit 'cc9a48c5b0ea10e2ebea18b5024e6bd40542c642' into react-enhanced-powerapps-codetour 2020-07-26 23:29:47 -04:00
.vscode
assets Added video links 2021-11-06 14:20:16 -04:00
config Adding PnP identifier for the MPN ID entries in samples - distinct sample usage in production 2021-01-07 14:51:39 +02:00
lib Added package, resizing, placeholder size fix 2020-08-15 15:06:40 -04:00
sharepoint/solution Delete index.md 2021-02-04 21:15:58 -05:00
src Added package, resizing, placeholder size fix 2020-08-15 15:06:40 -04:00
teams
temp Updated readme 2020-10-02 22:31:07 -04:00
tools
.csscomb.json
.editorconfig
.gitignore
.stylelintrc
.yo-rc.json
LICENSE
README.md Moved disclaimer to bottom 2021-11-07 02:11:17 -05:00
gulpfile.js
package-lock.json Added package, resizing, placeholder size fix 2020-08-15 15:06:40 -04:00
package.json Added package, resizing, placeholder size fix 2020-08-15 15:06:40 -04:00
tsconfig.json
tslint.json

README.md

Enhanced Power App

Summary

Sample web part showing how to embed a Power App that resizes, adapts to themes, and supports dynamic properties

Enhanced Power Apps in Action

It also resizes the app to fit the web part dimension: Enhanced Power Apps reszing in Action

Compatibility

SPFx 1.11 Node.js v10 Compatible with SharePoint Online Does not work with SharePoint 2019 Does not work with SharePoint 2016 (Feature Pack 2) Teams Incompatible Local Workbench Incompatible Hosted Workbench Compatible

Applies to

Prerequisites

You'll need at least one application in Power Apps that you wish to embed in SharePoint.

Solution

Solution Author(s)
react-enhanced-powerapps Hugo Bernier (Tahoe Ninjas, @bernierh)

Version history

Version Date Comments
1.0 July 27, 2020 Initial release
1.1 August 15, 2020 Added improved resize event handler

Minimal Path to Awesome

  • Clone this repository
  • in the command line run:
    • npm install
    • gulp serve

To Use

  • Create a Power App
  • In your app's Settings page (under File | Settings ), select the application size that suits your needs best Application size.
  • Make sure to keep Scale to fit on
  • Once your app is saved and published, go to make.powerapps.com and find the App ID by browsing to Apps, selecting the app you wish to embed (select it, don't launch it) and viewing Details
  • In the app details page, find the Web link or App ID and copy it. Add web link or app id.
  • Add the Enhanced Power Apps web part to a page.
  • In the web part's property pane, paste the value you copied in the App web link or ID field.
  • In the Appearance group, select Maintain aspect for the Resize behavior and select the Aspect ratio that matches the application size you selected earlier Appearance

You can also use dynamic properties to pass values from another web part on the page (or page context information) to Power Apps and/or make your app change colors to match the SharePoint page theme and section color.

Features

This web part was created because the out-of-the-box Power Apps web part was missing some features that were important to me.

This Web Part illustrates the following concepts on top of the SharePoint Framework:

  • Theme awareness
  • Context awareness
  • Dynamic data
  • Property Pane HTML

Theme Awareness

The sample demonstrates how to react to changing theme colors and section background colors. It can pass theme colors to the embedded Power Apps application.

If you want to use a color within Power Apps, simply use Param() to retrieve the value that is passed to Power Apps as a parameter, then use ColorValue() to convert the string value to a color Power Apps can use.

For example, if you select to pass the bodyText theme color, you can use the following expression within Power Apps to set the text color to match the SharePoint text color:

ColorValue(Param('bodyText'))

Remember that parameters are case-sensitive in Power Apps. In the example above, make sure that you use bodyText, not bodytext.

Dynamic Properties

This web part is a dynamic property consumer. For example, you can bind the Enhanced Power Apps web part to a list/document library web part on the page and make your Power App display information about the currently selected item in your list/document library.

To configure it, follow these steps:

  • Add a List or Document Library web part on the page where your Enhanced Power Apps web part is located.
  • In your Enhanced Power Apps web part's property pane, expand the Dynamic Properties group Select the Dynamic Properties group
  • Turn on Pass dynamic property as parameter?
  • Under Dynamic property source configure the following properties:
    • For Connect to Source select your list/document library web part name
    • In the [Your web part name]'s properties select Column containing the filter value
    • In the Column containing the filter value, select the column that has the value you'd like to pass to Power Apps
    • In the Parameter name field, enter the parameter name that you'll want to use within Power Apps to retrieve this value. For example, if you selected the ID field, type ID.
    • Within Power Apps, use Param() and the parameter name you specified above. For example, if you specified ID above, you'll want to use Param('ID') within Power Apps to retrieve the value. Remember that parameter names are case-sensitive.

Note that the web part always sends the current page's locale to Power Apps via the locale parameter. You can use this value to create multi-language apps.

Property Pane HTML

This sample includes a PropertyPaneHTML control that you can use to embed custom HTML in a property pane. I use it to highlight syntax using the <pre> tag and to make text bold.

Video

Enhanced Power App Web Part - Cool Power App integration scenarios with SharePoint

Help

We do not support samples, but this community is always willing to help, and we want to improve these samples. We use GitHub to track issues, which makes it easy for community members to volunteer their time and help resolve issues.

If you're having issues building the solution, please run spfx doctor from within the solution folder to diagnose incompatibility issues with your environment.

You can try looking at issues related to this sample to see if anybody else is having the same issues.

You can also try looking at discussions related to this sample and see what the community is saying.

If you encounter any issues while using this sample, create a new issue.

For questions regarding this sample, create a new question.

Finally, if you have an idea for improvement, make a suggestion.

Disclaimer

THIS CODE IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR NON-INFRINGEMENT.