cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Advocate I
Advocate I

Filter stopped working, Not a valid connector Error response.

Problem: Yesterday a gallery stopped loading on two of my apps, they have been running fine with the code below  

Gallery items= Filter('[dbo].[NewTblAppTrips]', cmvLocationid=Dropdown5.Selected.LocationID&&'Trip Date' <Now()) 

Testing: I built a new app for testing, created a gallery and added (same) Azure SQL Cloud as my data source.

Gallery items= '[dbo].[NewTblAppTrips]' 

Gallery loaded no issues.
Changed to

Gallery items=  Filter('[dbo].[NewTblAppTrips]','Trip Date'>Now())

I got the following error. “An error occurred on the server. Server Response: Not a valid connector Error response.”

I have multiple DATE columns all gave same error when testing.
Filter does work on nondate fields.
Turned on/off Experimental Performance improvements, no help.
Also refreshed data source within PowerApps.
Limited Rows to 100
Conditions:
This is happening at multiple locations,  platforms and Apps.
 I saw nothing odd within the Azure portal.
Under Connections Azure SQL Server Status is “Connected”
Trip Date Data Type datetime2(0)
Table has 300 Rows
Ideas:
Did Microsoft change something?
Is my Filter missing something?
Any ideas or comments are appreciated.




7 REPLIES 7
Highlighted
Helper III
Helper III

I am experiencing the same issues.  I have narrowed it down to the <, >, >=, and <= symbols. If you test with = or <> the filters work.  But none of the others. 

Highlighted

I got the sasme results as you = and <> filters correctly.

Highlighted

There was a new release 3.19074.24. I am wondering if something changed. All of my filters worked correctly last night, but today nothing works. I collect all of my data based on dates for my app.  This is a huge problem that this isn't working. 

Highlighted

Update, filter works on Sharepoint list but you get a Delegation warning.

Filter(tblAppTrips,'Trip Date'<Now())

Can some else from the community support team confirm the same results on Azure and Sharepoint.

Highlighted

Hi @cmv ,

Is your data larger than 2000?

Deleagtion is PowerApps itself limit. PowerApps could only deal with 2000 records locally. If your data is large, you should use delegable funtions. Or else your result may not be right.

If your data is larger than 2000, you should modify your formula and use delegable funtions:

https://docs.microsoft.com/en-us/connectors/sharepointonline/

If your data is smaller than 2000, the delegation warning will not effect your app performance.

Just do not remember change the non-delegable limit to 2000.delegation.jpg

 

Best regards,

Community Support Team _ Phoebe Liu

 

Community Support Team _ Phoebe Liu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Highlighted
Frequent Visitor

I've got the same problem. Any news on this?

Highlighted
New Member

I am currently getting this same issues as a well in a new app a I am building. I have used this before and it worked. Same error message as well. Defiantly does not like the = sign. 

Helpful resources

Announcements
Community Conference

Power Platform Community Conference

Check out the on demand sessions that are available now!

News & Announcements

Community Blog

Stay up tp date on the latest blogs and activities in the community News & Announcements.

secondImage

Power Platform 2020 release wave 2 plan

Features releasing from October 2020 through March 2021

Community Highlights

Community Highlights

Check out the Power Platform Community Highlights

Top Solution Authors
Top Kudoed Authors
Users online (6,759)