Another outage / bug - Drop down lists not working any longer

[hedborg]

There seem to be another random outage / bug created on Microsoft's side afflicting unchanged apps that have been working for months.

Suddenly all my drop down lists are not working any longer.

They are fairly simple ones connecting to an underlying Azure DB, e.g.:

Items = Filter('[dbo].[Status]';Active)

"Not a valid connector Error Response".

It seems like removing the Filter(), might solve the error, but historically these kind of changes just have to be reversed as Microsoft later realizes that it actually should work.

What's the status this time?!?

[Maurik]

Hi, since this morning we are having exactly the same issue.

[hedborg]

I ended up with (temporarily) removing all Filters/Sorting, which of course leaves a crappy app, but at least it works.

My experience is that Microsoft realises that was they have messed something up in a day or two and then functionality is restored, so “waiting” is of course an option if you have a lot of drop downs (and non urgent needs...).

Unfortunately this is not the first time I have experienced problem like this with PowerApps, which is far from optional in a production environment.

[v-yutliu-msft]

Hi @hedborg ,

I've made a similar test but not met the same problem like your description.

Please check your connection's condition and your network's condition.

Try to recreate your conncetion and work in a good network condition.

I've reported your issue to our product team.

If there is any improvement, I will reply here.

Best regards,

Community Support Team _ Phoebe Liu

[hedborg]

Hi,

The following Filter was suddenly not working:

Filter('[dbo].[Status]';Active)

Now I instead tried:

Filter('[dbo].[Status]';Active=true)

Now that is suddenly working.

"Active" is a bit in Azure SQL.

Amazingly similar problem to this one 6 months ago, but the opposite way around...:

https://powerusers.microsoft.com/t5/General-Discussion/Filtered-Galleries-are-no-longer-working-sinc...

What's the recommended way of handling bit? How come the logic is changed every now and then?

Kind regards

Niklas 

[nando1]

Hi all, 

is there an Update on this? My Filters do still not work as before. It seems like the logic changed. I was trying to recreate my formulas with the new logic but it takes a while, because it seems to be more complicated than it was before. Would be nice to hear something about the status on this.

Thanks,

Nando

[hedborg]

Any update on this?

Kind regards

Niklas

[saychiraj · Accepted solution]

Hello,

We recently made some performance improvements to SQL connector as a result of which we lost the ability to specify Filter('[dbo].[Status]',Active) as it translates to incorrect SQL. It is a performance tradeoff.

The right way to specify the filter here is,

Filter('[dbo].[Status]',Active=true)

Thanks!

[hedborg]

There is finally a response in this thread, which basically states that a bit can no longer be used as just e.g.

Active

but has to be

Active=true

I changed my filters quite early back to this logic and they have been working since.

Kind regards

Niklas