I have a Power App I've been using for at least a year, maybe two, and it has a button which performs the equivalent of the following. I've simplified it a bit for the purposes of this forum post, but this simplified version exhibits the same problem:
ClearCollect(MyCollection, Filter('[dbo].[Tasks]', ID = 209 )
The "[dbo].[Tasks]' table has 3 columns - ID, ID_Client, and Task. The problem is that only the first two of these are being loaded into my Collection - the "Task" column is being missed out. If I remove the Filter, and just do:
ClearCollect(MyCollection, '[dbo].[Tasks]')
...then it works fine - all three columns are returned. So it looks like something weird to do with the filtering operation. If I use the PowerApps Monitor tool to see what's going on under the hood, the "x-ms-request-url" is being set to the following (have redacted the server and database names):
/apim/sql/23cd4685c08249129ca710527d3ee0df/v2/datasets/servername.database.windows.net,databasename/tables/%255Bdbo%255D.%255BTasks%255D/items?%24filter=ID_Client+eq+209&%24select=ID%2CID_Client&%24top=500
The "%24select=ID%2CID_Client" part suggests to me that only the ID and ID_Client columns are being requested from Azure SQL. As I say, this has been working for well over a year, and it's not exactly complicated! So I'm wondering why it's not working. Am I missing something? Is it just plain broken at the Microsoft end?
The original Power App used v1 of the SQL connector. But I get the same problem with v2 of the SQL connector, and a completely new test Power App created from scratch.
