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 · March 21, 2016 ·
Using SQL Views in PowerApps is now available. See the blog to find out more: https://powerapps.microsoft.com/en-us/blog/using-sql-server-views-in-powerapps/
I am not a developer but I have learnt AWA to take my business to the next level and with all its limitation, AWA have been great tool of relashional database.
Obviously, the future is CDS per Microsoft, which is not ready yet. AWA is shutdown by April 2018 so my data will be lost. If you read about AWA retirement, there are tons of comments asking Microsft postpone shuting down AWA until CDS is ready! Please help make someone hear us on this.
Please also help confirming that CDS will have: -
1. Query (within the browser portal)
2. Like AWA table Data macros, i mean a tool that changes something in an entity based on a change in another entity apart from PowerApps. A program Manager at PowerApps has promissed me that this is on the road map!
3. Choose the Display Field from Related Entity: In an Account Gallery for instance, what does it mean that the account's default contact is Contact001? I need to see REAL NAME or email or combination. simple.
4. Calculated Fields
5. Freedom of mapping Outlook CDS add in to the entities I want, as I am not using and will not use the 6. 6. Default entities, so what is the point being unable to choose my data mapping?
Do you have any forecast regarding the availability of this feature ?Especially the ability of loading SQL views within microsoft flow & power apps ?
YES YES PLEASE
It is difficult to understand why access is limited tables only. We need views.
This is absolutely a must have. I can't actually proceed without views - I need to display JSON content in a relational format.
enquiry SQL Query is a must for continue develpoment on PowerApps, since
I am working on fixing problem on delegation. we usually use addcolums to join different table.. this is pool and slow method, but no other option can be found.. but one big problem is,
addcolumn function is only support for first 500 records, so that, if table is more than 500+ record, the joining is meaningless and useless..
In Short, we can not join tables which more than 500 records.. ho no..
if PowerApps still not support to enquriy SQL Query. the powerapss will not be successful
Not sure if/when we will get SQL query support, but in the meanwhile here is some good news:
We should soon be able to cache up to 2,000 rows. For me this will make a big difference.
Also, the blog clarifies some important issues in relation to server calls.
Has microsoft been able to let user to create PA from Views or Queries yet? Could anyone answer this question please?
Has microsoft been able to let user to create PA from Views or Queries yet?
No may be it is a sort of marketing limitation in order to promote the use of Common Data Service that wil soon (or does) enable n to n relationships (Not included in 365 so you have to pay for it) ? Powerapps team is a very reactive and inventive team, it is very stange that we have not any comment about acces to views, I cannot see the difference between tables an views if they restrict to read only and let the use update directly the underlying tables with Patch. May be we are not told everything !! :))
UPDATE 1 Feb 2018: By releasing this feature (access to SQL Server Views)
PowerApps Team demonstrated bravely that they put cusomer needs first !!! Bravo !!!