Forum Discussion
MicrosoftSharePoint Modern Lists - going to 10% of First Release tenants
- You can disable completely the new UI using PowerShell...see this: https://support.office.com/en-us/article/Switch-the-default-experience-for-lists-or-document-libraries-from-new-or-classic-66dac24b-4177-4775-bf50-3d267318caa9?ui=en-US&rs=en-US&ad=US
I'm trying to give power apps a try from the new lists but whenever I click to Edit in Powerapps I get a security certificate warning. Any ideas?
I'm also interested in whether I can remove the PowerApps and Flow options, at least for some lists. Are these options linked to the manage lists permission or site collection admininstrator level?
- Kerem Yuceturk
Hi Sian Busby, sorry to hear about the error. We did have an issue with the Edit button that we are fixing this week. In the meanwhile, you should be able to go to https://web.powerapps.com and find and edit all of your apps there.
Also, let me repeat my earlier answer about the button availability: We have heard the feedback about hiding the buttons from other customers too, and we are implementing a change that will tie these buttons to the "Preview Features" switch found in SharePoint tenant admin. This should be there before the end of the month, if not sooner. So you will soon be able to switch the "Preview Features" off, and remove the buttons from modern lists ui.
In the future, we are planning to govern these via a policy page that governs data access to SharePoint that we are building.
- I don't think you can remove both actions from the new list UX (at least currently)...have you tried both actions in different browsers? In one of my tenants with IE, I'm not having problems using both Flow or PowerApps actions
Are you sure we cannot remove the PowerApps and Flow options for lists ? It will be a big deal for us if this cannot be removed.
- It might be a problem at our end, thanks for confirming its not a global issue.
There are interesting things going on in regards to Flow and PowerApps and I'd like to share some of my notes, and look for validation.
1- Flow: I found out that It is fairly easy to control access to Flow. If a user doesn't have the license for 'Flow and PowerApps', s/he can not access to Flow. User will be prompted with a warning that says "The user with object identifier 'SOMEGUID' in tenant 'SOMEGUID' does not have an entitlement to use Power Apps". Licensing give some level of control to usage of Flow, and user can not continue to design surface. Note: Error message probably needs to be cleaned up a bit for clarity. GUIDs scare regular users.
2- PowerApps: This is where things get a little interesting. If a user without a license clicks on Power Apps, s/he gets a bit less gracious error message initially. "Error creating app from data. There was a problem saving your PowerApp to the cloud. Please try again." I am not sure if that initial error message is consistent behavior or it happened once.
However, after clicking CLOSE to this warning, user is presented with the PowerApps design surface and everything continued to function normally. This was a big wow moment for me.
Continuing my tests, I found out that without a Flow & PowerApps license user was able to create a Power App, save and publish it, and later make it public for other users. Please keep in mind, that test user had only "member" level permissions on the site collection, nothing else.
This is the part that's very concerning when you consider a big tenant with thousands of users. If users start building Power Apps that at some point their businesses depend on it (similar to workflows, and workflow solutions) - all of a sudden you can guess the challenge thrown at an IT organization to support these PowerApp solutions created, without any visibility to them. You can see how things will get really hectic, rapidly.
I believe in order to build sustainable solutions, IT organizations need to have some level of control to pace new functions introduced in SharePoint Online to their user base. We have to keep in mind that, although these are fantastic tools to empower users, without proper training and guides, all we are doing is creating an havoc on support teams. We have over and over again proven that providing regular users any level of somewhat complex tool without proper training guide, support expactions and general governance policy, is like handing a kid a loaded gun. It simply isn't good, and no good outcome can be expected out of it. I believe these new tools (Flow and PowerApps) need proper exposure controls to help IT organizations define the governance framework around them.
If there are controls and I wasn't able to figure them out, I'd like to get more information regarding to them, so that I can plan and pace the exposure by defining a proper governance framework before things get out of control.
PS: I had some difficulty using Chrome as a browser accessing PowerApps, button were not visible. IE functioned properly.
