SharePoint List Filter

[Bahalzamon]

Hello, I am attempting to filter a SharePoint list as Items within a PowerApps pull down. The list has 2 fields, Name and Used. I want to filter the pull down to only show where the Used is yes or true. I have used PA a few times and filter, still no go, unsure the problem. here is what I have tried:

• I originally had the Used column as a Yes/No. But the result was no options. My only guess here is that PA is still in its infancy this hasn't been implemented and/or corrected.

Filter('Members',Used)
Filter('Members',Used=true)

• So after ensuring the SharePoint list can be filtered and filtering it by the Name column I changed the Used column to a choice pull-down with Yes and No as options. Just gives me a delegation warning. I am assuming due to it being a pull down.

Filter('Members',Used="Yes")
Filter('Members',Used.Value="Yes")

• Also tried changing the Used back to a Yes/No box and creating a new column called PA and did a calculated column of =IF([Used],"1","0") so I can filter it based off of a text value. Same issue. I am guessing because it is a calculated field.

Filter('Members',PA="1")

The only thing I can think of would be to change the PA field to just single line of text, attach a quick and dirty Flow to the list and basically when the item is created/modified to populate the PA field with either a "1"/"0" or "Yes"/"No".

Per what I have found the above should work, but any suggestions would definitely help. 😃

[RandyHayes]

@Bahalzamon 

Actually, I might refer you back to your very first formula.  That should work perfectly (as I use that very often).  So, might want to look into what is causing it to not work for you.

If you are using this for a ComboBox or DropDown, make sure you are specifying the proper column to display.

If you're ever having problems that you want to do a quick check if things are working properly, you can do one of several things...here are two:

1) Put a Gallery on the screen and set the Items property to : Filter('Members', Used)  Then add a label to the Gallery and set the text property to ThisItem.Name...you should see results in the gallery.

2) Put a button on the screen and set the OnSelect property to : ClearCollect(testCol, Filter('Members', Used)), then Alt-click on the button and then go into the View->Collections and see that your collection is there and that it has the values you expect.

Also, consider that when you have added a datasource to PowerApps and then go back and alter the datasource, things get a little out of sync.  In most cases, you will be then needing to completely remove the datasource from your app and then add it back in...and even then, you still may have some hurdles to jump.

I hope this is helpful for you.

[Bahalzamon]

@RandyHayes I appreciate the quick response. 😃

But!!! Still a no go. I deleted the column, recreated it, nothing.

I even went and created a new App from blank, and did your 2 suggestions:

In the gallery I put a label with 'ThisItem.Name & " - " & ThisItem.Used' which works perfect, but as soon as I apply the filter, empty. Removing the filter it populates with everything.

As for the button, nothing, the collection is created with all the columns within it based on the list, but has no entries. Now if I strip out the filter on the button it populates with everything no issue.

Looking at the data within the collection with no filter it is reading them as True, so I am completely stumpted...

Any other suggestions? =(

[RandyHayes · Accepted solution]

@Bahalzamon 

So, after all the different tests on the list that you did...what is Used now?  I had assumed it was a Yes/No column.  Is it something different?  

If so, your Gallery test should have shown "whatever name - true" (or false).  Is that what you were seeing and what the column is?

Also...I apologize that in my rush of thoughts, I forgot the most important factor...there is an issue with the SharePoint Yes/No columns in PowerApps.  You can read about the details and some suggestions in this idea posting.  I added some to that post and my suggestion was (and applied to your case) to look for the NOT of the opposite of what you want.  So, change your formula to this:

Filter('Members', !(!Used))

This will filter by the Not of the Not of Used, which would be the same as anything that is true - Not true = false, Not false = true.

[Bahalzamon]

@RandyHayes Thanks again for the reply.

The Used column is a Yes/No checkbox. Using the Filter('Members',!(!Used)) works but I get a perminant "Delegation Warning" which I not a fan of as some of my other lists are large and I prefer not running into any issues.

I did test with a basic Flow and a single line containing a text value of "1" or "0" that works, but again it requires a Flow.

I think I will possibly use a combination of both as the double Not's for short lists and a flow for the long lists.

Unless you have any better suggestions?

[RandyHayes]

@Bahalzamon 

That was going to be the next question...is delegation an issue?  And the answer is "sometimes".

So, the answer to that is exactly as you mentioned.  You will need to use Flow or WorkFlow to populate a text or number column which is delegable and then filter on that. 

Until they fix the boolean issue with yes/no columns, it is the only workaround today.

[Bahalzamon]

@RandyHayes  Thanks again. 😃

OK, I'm going nuts, any idea why the Delegation warning comes up with the exact same scenario for a different list that is identical just with different information?

Whats up with the "sometimes" ???

I was thinking using the !! you get that error, but using the Flow I didnt get that issue, but it seems to be a coin flip. Does the error randomly go away as well? or should I create 20 lists and whichever one doesnt have the issue just use that one? LOL

[RandyHayes]

@Bahalzamon 

What I mean by Sometimes is that you seemed to indicate that some of your lists would have this issue based on their size and other not, so sometimes you will need to worry about delegation.

I would be suspicious if delegation warnings comes up differently...there is almost always something that is different that would cause it.  There are a lot of things you cannot delegate.

So, if you have specific ones, feel free to reference them and we can take a look.

[Bahalzamon]

@RandyHayes 

I appreciate all the assistance, as for differences between the lists they are literally identical minus the name of the list and actual data, they just have Title and Used.

But I have found an alternate way to resolve this issue and even using a completely seperate 1200 plus list do not recieve any delegation errors and it takes only a couple seconds.

Using a PowerApps Initiator > HTTP Request > Parse JSON > Response. This allows me to apply filters, sort, anything I want. It did take me about a day to get it all figured out as I was also pulling a lookup column which was not within my tutorial I found.

Heres the instructions I found: Filtered items from SharePoint to PowerApps using Flow

This helped me figure some of the info from the above tutorial: OData Documentation URI Cconventions