PowerApps Standalone App versus Customized List Form
There are two types of PowerApps canvas apps, and it may not be obvious that these are two different things, but it is IMPORTANT that you understand this BEFORE creating a PowerApp.
A common point of confusion when creating PowerApps, is the difference between the two different types of apps. First of all, most people do not even realize that there are two different types of apps until it is too late.
- When you go to a list in SharePoint, and click the PowerApps menu and choose Customize forms, you are creating a customized list PowerApp. The same thing can be done from list settings –> Form Options.
- When you create a PowerApps in any other way, such as going to web.powerapps.com, and clicking Create an app, or Make this app, or even if you go to the SharePoint list and click PowerApps –> Create an app…. all of these other ways will create a standalone app.
Once you’ve created an app using one of these two methods, there is not an easy way to switch it to the other kind of app. So, it is very important that you choose the correct kind of app right when you get started. At the end of this article, I will mention a very time consuming way it can be achieved, but it is definitely not a simple click of a button.
Here’s a further explanation as to what the two different types of apps are, and why you would choose one over the other.
Customized list forms
Did you go to a SharePoint list and click PowerApps -> Customize forms? If so, you are using a customized list form, and not a standalone app.
Permissions:
In order to control who can use the app and edit the app, it’s simply a matter of using SharePoint permissions. People who have Edit permission will be able to design/customize the PowerApp, and people who have Contribute permission will only be able to use the PowerApp, which entails filling out the form as an end user. Note that by default on your SharePoint site, all members of the site have EDIT permission on the whole site. You may want to change this to Contribute, at least for any list where you don’t want them designing the app.
End user interaction:
To use this app, it is simply a matter of going to the list and adding or editing items in the SharePoint list. This PowerApps is the list’s default form. If you don’t want users going to the list or seeing the list, there is no reason to create this type of app.
Mobile:
If the PowerApp has been embedded on a page on your site, using the PowerApps web part, End users can go to the SharePoint mobile app, and go to that page to use the customized form. These types of PowerApps will *not* be listed in the PowerApps mobile app.
* 3/31/2019 update: Apparently it does not work in the SharePoint app anymore.
Designing the app:
You can only design the app by going to the SharePoint list, and customizing it from there. This app will not be listed along with your standalone apps at web.powerapps.com.
Backup / Export of app:
This is not possible with this type of app.
Versioning:
Click File –> Save, then click See all Versions
QUICK TIP:
If you would like to get the App ID, which you may need for using this app in the PowerApp web part, from this screen, click the Details tab, and check out App ID.
Standalone Apps
Permissions:
You have two options for the type of roles you can give to users.
User – Allows them to use the app. This is what your end users need to access your app even if you embed it on a SharePoint page
Co-owner – Allows them to edit and design the app and publish changes to the app. This is ideal for any fellow developers that need to help you build the app.
When you first add someone, they are “User”, then when you check this checkbox, it makes them a co-owner. Optionally send them an email, too.
End User Interaction:
Some ways that end users can get to the app, to use it:
- Open the PowerApps mobile app on their device. You can even pin your favorite apps to your home screen.
- Go to web.powerapps.com, and peruse the list of apps, and open any app they need to use.
- Click the app launcher (waffle) menu at the top left in Office 365 and click PowerApps to get to the list of apps
- Provide the end users the URL to directly go to the app. This can be found on the Details screen (see image below).
- Create a button on your SharePoint page, using that URL, for users to go directly to your app.
- Use the PowerApps web part to embed your app on any page in SharePoint.
Mobile:
Install the PowerApps app from the app store, and authenticate to your Office 365 tenant, then see the list of apps that have been shared with you.
Designing the app:
Go to web.powerapps.com, click the ellipsis next to your app, and click Edit. See image below. You can only edit the apps where you have either created them, or have been given the Co-owner role.
Backup / Export of app:
Go to web.powerapps.com, and click the Export package button. See image below. Give it a name, and click Export. It spits out a zip file. Then, go to another environment or tenant, click Import package, and upload that zip file.
Versioning
In your list of apps at web.powerapps.com, click the Details button on any app.
Then go to the Versions tab.
Here is a quick table, summarizing these points:
| Customized list form | Standalone app | |
| Permissions | SharePoint permissions on the list | User or Co-owner |
| End user interaction | On the list | from the list of PowerApps, or using a direct link |
| Mobile | In SharePoint app, if embedded as a web part | In the PowerApps app |
| Designing | From the list, customize list form | at web.powerapps.com |
| Export | Can’t be done | at web.powerapps.com |
| Versioning | save, then see all versions | from the app’s details screen, web.powerapps.com |
Thanks for reading, I hope this was helpful to you!
4/20/2019 update: I love April Dunham’s post, Open PowerApp using SharePoint Column Formatting. You can get the best of both worlds with this solution!
If you do need to try to “convert” one type of app to the other, it’s going to be a matter of copying and pasting. Create a new app, and open each app in a separate browser window. You can copy and paste in controls and even screens. You may even want to group controls together before copying, if you don’t want the whole screen, just some controls. And of course, re-create your data connection(s) in the new app.
Are you brand new to PowerApps, and interested in getting started learning some fundamentals? Try out my
FREE 5 day PowerApps Beginner Email Course
Beyond beginner? Check out my full (12 hour) PowerApps training class!
Hi,
Can we add the script on the List Forms. I need to run some script on from form load.
Please let me know my options ?
Thanks in Advance,
Sadhana
LikeLike
No, no script in PowerApps, use PowerApps functions and formulas. The OnStart property is where you’ll put those.
LikeLike
Hi Laura,
I work for the State Government and Flow and PowerApps are not yet available in our tenant. We are using the trial license for both Flow and PowerApps. With Trail license, I don’t see an option to customize list form from the custom list. I have to go to the web.powerapps.com and create an app which is what you explained as a standalone app. The app connects to my SharePoint list. From what I understand, Flow and PowerApps will be disabled to users, by default. It is only assigned licenses to designed people. Does it mean if we have a customized list form, does it mean Flow and PowerApps don’t need to be enabled to users in order for them to submit the request (they only need contribute permission to the list)? If it is a standalone app, the app will need to be shared with users and do PowerApps need to be enabled to those people that the app is shared with in order for them to view the app?
PowerApps web part is still not yet available to GCC.
Thank you for you reply.
LikeLike
Hi Laura,
for the standalone app, the user also needs permissions on the SharePoint Lists the app interacts with. To my knowledge the users needs minimum Edit permissions.
LikeLike
Yes, that’s true. The info I was writing about was just how to share the app / who can open the app itself. So yes, to be able to do anything with the data like see it or edit it, the users do also need to have SP permissions on the list(s).
LikeLike
Hi Laura,
How handle SharePoint user permissions on standalone power apps. Ex: User have read only access in SharePoint site will not be able to add/Edit Items in power apps.
LikeLike
Hi I’m not really sure what your question is. Yes, users who have read-only access in SharePoint won’t be able to edit items in the PowerApp. This may be helpful… If you have, say, an “EDIT” button in your standalone PowerApp, and you don’t want the read-only users to see it, you can hide it from them using this formula in the Visible property: DataSourceInfo.EditPermission
Does the logged in user have edit permission to this data source? True/False. So, therefore, the button will automatically be hidden from people who don’t have edit permission.
LikeLike
My “app” is losing connection to the list and I cant save items / edit or w/e. I havnt used powerapps in almost 2 years since it worked so bad and it hasn’t got better. Don’t use this people. My worst decision 2019.
LikeLike
It was crap a couple of years ago. I refused to use it back then. It tremendously better now in 2019. (in my opinion)
LikeLike
Anyone confirmed that the sharepoint form work in the sharepoint app? I have been trying and its asking to sign in again. Then when you click that it says to allow popups. Then it just breaks. Has anyone gotten this to work, or am I missing something?
LikeLike
Apparently it used to, and does not anymore.
LikeLike
Hi,
My requirement is to implement a big supplier details form in PowerApps having different sections. These sections have multiple fields. The editing rights for these sections depend if the user is part of particular sp group, eg: Finance, Quality, etc.
Also, along with this, I want to create FLOW for approvals of new/update supplier cases.
In your opinion, should I go for Standalone or customize form options?
Any help is appreciated.
LikeLike
Always standalone.
LikeLike
Hi, Laura. Thanks for a great article. Is a PowerApps license required for a user to access and submit the PowerApps form for both methods? Somewhere I heard that if you customize a list with PowerApps, you do not need a PowerApps license to complete the form. That doesn’t seem to be true. We have a large organization (120+K users) and we will be licensing over a long period of time. Thank you so much.
LikeLike
I don’t know what your Office 365 license is, but I have E1 and PowerApps is free with it. There are certain “premium” features of PowerApps and Flow, like certain connectors that require “plan 1 or 2” but most likely you won’t need that.
LikeLike
Hi Laura,
Great article. Unfortunately I still think that PowerApps is missing one critical element – when a user goes into the SharePoint app on their mobile device and go into the list, they still see the out-of-the-box view/edit forms.
If you create a customized PowerApp from within the List it doesn’t reflect in the mobile app via the SharePoint app.
If you create a standalone PowerApp it still doesn’t reflect within the SharePoint app.
I’ve customized a list to use Tabs and hide/disable some columns depending on a status value and user permission level (based on some of your great tutorials :)).
But there is no way that I can use this solution as a user might bypass SharePoint Online and PowerApps and go directly into the SharePoint app on their mobile rendering the entire solution useless.
Hopefully I’ve made sense, and hopefully I’m completely wrong (please please please let me be wrong).
Question is – how do we get the list to use the custom list forms from the SharePoint app on a mobile device? If we can’t do that then PowerApps is a fail for so many scenarios that people may not realize until it’s too late.
LikeLike
Hi Laura. any ideas on how to make the app without the end users being able to access the full datasource? I’m having the issue that some info on the datasource is not shareable with all users(for security reasons)
LikeLike
You can set the default view of the SharePoint list to be filtered by something that will never show any items, like ID=0
LikeLike