There is no Reset property to galleries that when toggled will reset the selection to the Default item.
This is strange since Reset is present for example in text inputs and other controls that also have a Default property.
Please add the Reset property to galleries.
It would be good if we can get an option to validate whether the input value is valid Telephone Format or Email Format.
I would suggest to give an ability use RegEx or an option to validate the possible different validations (such as email formats, telephone formats, ip adress etc.
If the point of PowerApps is to promote building of "Enterprise" Apps, then surely you need to have access to Sharepoint Document libraries that only authenticated Users can access.
Currently you can only view PDFs that reside in libraries that allow anonymous access, quite pointless in an Enterprise environment. That makes this feature useless for most of us.
This one feature would really open a whole lot of possibilities in Enterprise scenarios, especially when trying to wean Users off e-mail oriented workflows.
My main blocking point right now, is that I can not attach files to SharePoint list via PoweApps edit forms.
I can create app which can manage orders in SharePoint list for my company in few seconds, but we are forced to keep original email request in list. For this we are using InfoPath which works fine, but PowerApps should be much more suitable solution.
Also we are using same procedure but with excel forms, for that is also important to be able to EDIT excel/word... attachment directly on SharePoint. So what I would like to have in DisplayForm/edit form, when I click on excel file attached, it will open my excel, let me edit it and save it back directly to SharePoint like is possible now with forms on SharePoint.
Once I will have those 2 things in PowerApps, my live will be much more easier!
Would like to use PowerApps in our company, but right now... its not possible
Currently, users are able to create, read, write, delete entities.
I am suggesting that PowerApps distinguish between reading data in the app and reading data in Excel (downloading the entity and opening it in Excel). As it is right now, users that you allow to Read can do both. I think that is a major security concern.
I filter all data that comes through all of my apps. I presume that everyone does as well--it is hard to imagine working with entire data sets all at once. I want my users to be able to filter all that data in app so I have to enable Read, but it's filtered on purpose: I don't want them seeing everything else. If PowerApps eventually allows the making of public apps, you also would not want your data freely downloaded and viewed.
That is why I am suggesting:
- separate the "Read" permission into Read in PowerApps and Read in Excel or
- provide a way to enable/disable downloading of an entity as a permission
it would be nice to be able to use this to request data from individuals not within our company - and submit that data into a sharepoint list.(or SQL)
SQL Server, Sharepoint, Salesforce and CDS are managed connectors having 'tabular' capabilities. This means these connectors light-up aditional PowerApps tooling at design-time for named entities such as 'choose table' pane when adding the datasource and the abilitiy to use as the datasource of a form control. There is also additional abstraction which enables the tooling to map CRUD operations for entities.
None for this is documented so developers cannot presently add 'tabular' capabilities to Custom API connectors.
We need the ability and guidance to create Custom API connectors having the additional abstraction needed to make PowerApps understand that the API has 'tabular' capabilities.
Adding barcode and driver’s license scanning would be a great addition for warehouse and banking applications. Both are standardized and would allow for less manual entry.
Evan Chaki shared this idea · December 17, 2015
Hello all, it would be great to have an action to be able to download a collection as an Excel file to the local device.
It is possbile to implement such behaviour with first saving the data to a file and then using Download, but this seems unnecessarily complicated.
On making the connection, I only see Tables, not Queries. This cannot be workable as Tables usually have many IDs and IDs are meaningless, Connection to Queries is a must: same as Excel and Power BI.
Yahya shared this idea · ·
Indeed, innovative non-developers have great ideas and this tool empowers them to easily build UIs with my APIApps for a backend.
But with ease of use comes limitations - inevitably many PowerApps will need functionality that the PowerApps designer cannot handle. At this point the app needs to be exported and extended using Visual studio or other dev tools.
With Siena this was somewhat available by cracking the .appx.
We need this or better for PowerApps.
joshbooker shared this idea ·