I would agree whole-heartedly with the need to extend "delegation" in PowerApps but would suggest that developers really need a fairly robust data layer in PowerApps - a la query capabilities in MS Access. Within my company, we are evaluating PowerApps for development and this gap leaves us wanting. The current design is very limiting.
Publicizing a timeline and basic design concept for improvements to make PowerApps more capable would help a lot.
Hi @GenoRock, I would beg to disagree. As it is, the querying language of PowerApps is already quite powerful and works fine, or at least it would/will once the bugs are ironed out and delegation is extended.
For Access-like querying I would suggest the more robust solution is to do the querying on the server side (i.e. SQL or whatever your database is running on) and create a view. The problem with that is that PowerApps at the moment cannot connect to queries/views as a data source, but I cannot believe that this capability is not on its way, since it is the first or second most requested feature.
Your alternative is also good, and I guess it would be to just allow the data source to be defined in SQL, for example.
I normally dont comment on forums, but the 500 row limit is just too frustrating to ignore. If Microsoft is using powerapps for educational and learning purposes, then I can understand . But, for even medium scale enterprise level application, Microsoft needs to step up and provide a very clear direction. PowerApps is a great initiative and for its large scale adoption, I strongly recommend taking care of these issues that usually make the difference between adoption and rejection of an emerging technology.
@Meneghino--thanks! Your blog is very thorough with work arounds too. That saves me from having to come back here to ask for every limitation I hit ๐
