Share your ideas and vote for future features

Problem: One of the biggest issues in PowerApps right now is that we cannot protect our data. If we connect any data source to PowerApps (Excel, SharePoint List, SQL Server Connection) it has to be shared with all users for them to be able to use the app. This creates a problem where user has access directly to data source and can bypass the app to do direct modifications to the data source as well as see information not meant to be seen by them. If your app was built to limit users access to some data, for example: Showing users only their vacation requests and hiding other user vacations Showing user only their travel request and hiding other user travels That means that all users can see all data as well as they can modify it without any trace.   In case of Excel file on OneDrive we need to give users access to this file, that means that user can just go on OneDrive and find the excel file and edit it. In case of SharePoint List, that means that user needs to have Edit rights to that list and can just find it on the SharePoint Site and go in and edit. In case of SQL Server Connection, that means that user can open PowerApps, click create new app, open Data Sources and the shared SQL connection will be there and he can connect to it. This will allow the user to see all tables in that SQL connection with edit rights.   Idea: I believe the best way to fix it, and this will allow PowerApps to become truly powerful tool to replace most of organization applications is to give the App itself write rights to the Excel sheets, SharePoint lists or SQL Connection and not the user. This way the user will have no access to the files, SharePoint List or SQL Connection and the only way to interact with data will be through the App. ... View more

Problem The biggest problem with developing PowerApps with Azure SQL Database is that we have to share the SQL Connector with each user of the app. What that means is that each employee can bypass the app by creating their own app and adding this connector to their app (since it is shared). They get the ability to see all the tables and views in the database. Basically, everything there is in the SQL database, on top of that they also get the ability to edit the information in any way they please. This is not an issue for non-confidential information and simple apps. However, we have plans to develop more complex apps with data that should not be seen by everyone who will be using the app. PowerApps is great as we can build custom logic on who sees what. However, since each employee can create a fake app and throw in the SQL connector that was shared with them, this means that all the security and complex data validation built in the app becomes useless.   Idea I think the simplest solution would be to make the SQL Connector when sharing it, the user gets “Can use” permission, it would be great if we could give an even lower permission level like “Can use only in this App”. This would make it impossible for them to create fake apps and throw in this SQL Connector to see data they are not supposed to see. OR Another option would be that when user has “Can use” permissions on SQL Connector they would only be allowed to use it where the owner put that SQL Connection, making it impossible for them to drop this connection in their Apps or Flows.     Either one of those solutions would make PowerApps a lot more useful for a large number of corporations. This would definitely push PowerApps adoption for more complex systems and bring it above other similar platforms out there. ... View more

I have received some feedback from my app users that it is sometimes hard to tell when image or text is clickable. On the desktop version, when you hover over an image the icon remains the same or when you hover a text it changes to the edit text icon, the mouse icon seems to change to hand icon only when hovering over objects like Icons or Controls like Button control.   Example 1 The text in the Org Browser by Microsoft says View My Profile, when hovering over it with mouse, the mouse icon changes to select text icon.   Example 2 When using images as buttons, the mouse will stay as a cursor and will not change to the hand icon.   Example 3 Hovering mouse over the button. It changes to hand icon and it is clear that you can click it.   This is not a problem on the Phone since you click with your fingers but it confuses the users on desktop. Would it be possible to make all objects with functions in OnSelect property to have a <a> tag or something similar that it would force the mouse cursor to change into hand? ... View more

Hide the Sharepoint button bar, so that we can instead put our own "Submit" and "Cancel" buttons at the bottom of the form. Creating a custom "Submit" button works fine at the moment, but a custom "Cancel" Button does not seem to work like it should.  However it defeats the purpose if users can just use the default save which does not have the custom actions. ... View more

to be able to have different powerapps forms for different content types in sharepoint list. so that all  can merge into a single item.   ... View more

Please provide the ability for the code editor to pop out into a SEPARATE, moveable and resizeable window.   ... View more