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/
And it looks like Queries are coming to PowerApps, finally, in Technical Preview, as of yet. Weird enough, they do not support CDS entities, what should be the first in the list!
Neat -- is there a release date for this?
Yahya - I looked at this again. I don't think that this is as helpful as it looks.
Everyone -- comment and correct me if I'm wrong, but here's what I see here:
This new (pending) query functionality allows for a wider variety of ways to import data into CDS. Of course it doesn't list CDS as a datasource to query from -- why would you use this tool to import data from CDS back into CDS? This is already something you can do.
Now -- for those of us who need to use our local SQL Server connections -- this may or may not be helpful. Currently, I can't use my on-premise connectors in the same Environment as a CDS connection. If this behavior persists, then this new functionality is 100% not useful to me. Even if I could go to an Environment using CDS -- I would never be able to get my data back into my database where I need it (I need it there because I have existing business softwares and infrastructure that depend on it to be there).
If this change comes with the ability to use CDS and On-Premise connectors in the same environment AND if there are then ways to sync the CDS with on-premise connectors: we may be getting closer to something workable.
Anyone have any definite information to support either of the bolded pieces above? We need both! Or, of course, we need the ability to see our SQL views like we've been asking for. 🙂
This maybe a deal breaker I had all my SQL done and was going to use views for list and lookups ... will explore more to see if it is worth continuing
In my personal opinion it is definitely worth continuing because there is a lot you can do already in shaping data with PowerApps functions, and because sooner or later (hopefully sooner) views should be available.
Frankly, the only thing I have no direct work-around for is patching null values back to a data source. The indirect workaround is to call a stored procedure.
PS The above is for Azure SQL DB, not sure about on-premise
@Meneghino What's your direct work-around for using views?
Hi @NEPatton, nothing too original:
1) Where possible I replicate the SQL logic of the views with delegable PowerApps expressions
2) If performance of 1 is not acceptable I cache where appropriate, using ForAll as a last resort
3) If all else fails, a timer job on SQL Server to materialise the queries as tables that PowerApps can read
What is an example of a view that you need to connect to? (We can take this conversation offline if you like and you can send me a private message)
I'm using On-Premise SQL Servers -- I'm applying all 3 of your work arounds. I was just curious if you knew something I didn't! 🙂
It is my understanding that the PowerApps team is going to allow us to utilize SQL Views in the future... do we have an ETA when it will be available with On-Premise connectors
Just had a response from Microsoft that SQL server views will be supported in PowerApps before December of this year!
Fantastic news for PowerApps users I am sure you will agree. When this support comes in PowerApps will become a 'killer app' for many businesses.