cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Combobox allows filtering of all matching results, not just exact matches

Hi, 

 

I have a screen with the top half (horizontally) acting as a multiple combobox filter area and the lower half is the gallery view of the matching results.  I'm trying to add functionality for the gallery to return all matching results from the Sharepoint list but it's only finding the exact matches.  I'm sure the formula needs to be tweaked...

 

I was assisted by another user a while back to create a gallery that gets updated from a TableData card that has the actual filter criteria.  This then updates the gallery.

 

The filter code in the "Update" function of the TableData is:

 

{
    TableData: Filter(
        Lessons,
        DBApproved = "Yes",
        (IsBlank(cboLLROwner.Selected.Result) || Owner = cboLLROwner.Selected.Result),
        (IsBlank(cboLLRWho.Selected.Result) || Who in cboLLRWho.SelectedItems),
        (IsBlank(cboLLRWhen.Selected.Result) || When  in cboLLRWhen.SelectedItems),
        (IsBlank(cboLLRWhere.Selected.Result) || Where in cboLLRWhere.SelectedItems),
        (IsBlank(cboLLRSuggested.Selected.Result) || SuggestedReviewPeriod = cboLLRSuggested.Selected.Result),
        (IsBlank(cboLLRResType.Selected.Result) || ResolutionType in cboLLRResType.SelectedItems),
        (IsBlank(cboLLRWhat.Selected.Result) || What = cboLLRWhat.Selected.Result),
        (IsBlank(cboLLRWhy.Selected.Result) || Why = cboLLRWhy.Selected.Result)
    )
}

 

 

The main gallery then has the following formula for "Items": 

 

SortByColumns(LLTableData.Update.TableData, "What", Ascending)

 

 

The only item that I need to alter is the "Who" line to allow it to match criteria found in the Who column where the departments are stored as departments separated by commas like, "Ops, R&D, MKT, MAIN".  If I select "Ops" in the combobox, it only returns records that only have "Ops" in the Who column.  I want it to find all records that have Ops listed either standalone or somewhere ( (any position) found within the departments listed in that column (i.e., R&D, MAINT, Ops").

 

Currently works like this:

Finds the records that ONLY has what is selected in the combobox (i.e., only returns Records 1 and 4 below)

Record 1: "Ops"

Record 2: "Ops, R&D"

Record 3: "AO, MAIN, Ops"

Record 4: "Ops"

 

Future State:

Finds ALL records that have the department selected in combobox anywhere in the "Who" column of the SharePoint list (i.e., Returns Records 1,2, 3, and 4)

 

 

1 ACCEPTED SOLUTION

Accepted Solutions
poweractivate
Most Valuable Professional
Most Valuable Professional

@JScherff 

 

I can explain this to you in detail with a specific example below: 

 

Suppose my SharePoint list of S5List01 below:

 

poweractivate_0-1670905585167.png

In this case suppose I want Listing A and B to be returned from the above (i.e. containing banana)

 

If I do exactly like you did,

 

Filter(S5List01,Listing in ComboBox1.SelectedItems)

 

poweractivate_1-1670905671143.png

I will get only Listing B as above and not both Listing A and B like I want.

 

The reason is because when the Filter is operating on Record A of the Filter,

I am comparing apple,banana,carrot (Listing) to see if it is contained within the word banana (an element of ComboBox1.SelectedItems) - and of course since the longer string apple,banana,carrot cannot possibly be a smaller portion of just banana this obviously returns false.

 

The only way that would return true is if the ComboBox's Selected Item itself had said apple,banana,carrot - do you understand?

 

So I should write the formula like this instead:

 

Filter(S5List01,!IsBlank(LookUp(Split(Listing,",") As ThisListing, ThisListing.Result in ComboBox1.SelectedItems)))

 

poweractivate_2-1670905985586.png

I get both Records in the Gallery I expected now, and B

 

The reason it works is because I first split the string containing all of the strings in it, into individual strings without the commas. 

Split(Listing,",")
This makes a Table. 

Next, I use the LookUp function, but rather than a whole data source or collection I just use the Table itself that was Split as the input table, using the As operator to name each individual element of the Split(Listing,",") Table as the name of my choosing, ThisListing.

 

So I have:

 

LookUp(Split(Listing,",") As ThisListing, ThisListing.Result in ComboBox1.SelectedItems)

 

Basically I say - From the outer filter, I have the column Listing accessible to each Record. Now take each comma separated Listing in the Listing column (that is a single string at the moment), and give me a Table of individual Listings (strings) instead, each string being a row of a Table and without the commas - that's what Split(Listing,",") does. Now take that Table, and LookUp for me , using each individual Listing itself as a convenience inner element called "ThisListing", and using something called Result that's inside it (this has to do with what Split did with the strings - each one of those individual strings without the comma, ends up as an individual row of a Table, in a single column called Result - that's why it's ThisListing.Result) - with each of these elements called "ThisListing.Result", check if it's contained inside of ComboBox1.SelectedItems.

 

This LookUp will either return one record (Not Blank) or no records (Blank)

Now I want to simply know if it's Blank or Not Blank, because I want to reduce the whole second argument of Filter to just true or false, which is what the outer Filter is actually looking for,  so that's why I use the IsBlank function wrapped around it. I've inverted it intentionally to !IsBlank

So if it is not blank it's true - if it is blank it's false

In other words, not blank means the LookUp returned one record - so it means that one of the individual components (not the whole comma separated string but one specific part of it as you want) has matched one of the ComboBox Selected Items - we want that situation included in the returned Records of the Filter so we want to check if it's not blank and if so, we want it included (true) - otherwise, if there's no match, we want it to return false meaning the LookUp returned no record, and so there was no match at all, and so it should not be included, but should be excluded from the Filter instead.

 

Does it make sense now @JScherff ?

 

Your Scenario

 

So @JScherff - in your specific scenario, I'd recommend something like this:

 

Rewrite your formula of

(IsBlank(cboLLRWho.Selected.Result) || Who in cboLLRWho.SelectedItems),

to something like the below instead:

 

//do something like this instead
(
       IsBlank(cboLLRWho.Selected.Result) 
   || !IsBlank
       (
           LookUp
           (
               Split(Who,", ") As IndividualWho
              ,IndividualWho.Result in cboLLRWho.SelectedItems
           )
       )
),

 

I have intentionally put a space after the comma for your scenario because it may not work without the space. Your examples of multiple departments seem to be separated by both a comma and a single space, rather than just a comma like in my example, that's why I use Split(Who,", ")

 

See if it helps @JScherff 

 

P.S.: I have intentionally avoided the use of the ForAll function here. (Try to avoid using ForAll for just its convenience of looping over things and for no other reason, especially if you try to use it just to loop over something but won't be using the output table of ForAll in any way. Even if it may "work", it's probably going to perform less efficiently that way, and it is not a good practice or habit to get into. In my case, if I had used a ForAll in this scenario, I would probably not have used the output table of ForAll at all, so I avoided using ForAll here. It may be tempting to use ForAll here, but it is better not to use it - so that's why I have not used it here).

View solution in original post

3 REPLIES 3
poweractivate
Most Valuable Professional
Most Valuable Professional

@JScherff 

 

I can explain this to you in detail with a specific example below: 

 

Suppose my SharePoint list of S5List01 below:

 

poweractivate_0-1670905585167.png

In this case suppose I want Listing A and B to be returned from the above (i.e. containing banana)

 

If I do exactly like you did,

 

Filter(S5List01,Listing in ComboBox1.SelectedItems)

 

poweractivate_1-1670905671143.png

I will get only Listing B as above and not both Listing A and B like I want.

 

The reason is because when the Filter is operating on Record A of the Filter,

I am comparing apple,banana,carrot (Listing) to see if it is contained within the word banana (an element of ComboBox1.SelectedItems) - and of course since the longer string apple,banana,carrot cannot possibly be a smaller portion of just banana this obviously returns false.

 

The only way that would return true is if the ComboBox's Selected Item itself had said apple,banana,carrot - do you understand?

 

So I should write the formula like this instead:

 

Filter(S5List01,!IsBlank(LookUp(Split(Listing,",") As ThisListing, ThisListing.Result in ComboBox1.SelectedItems)))

 

poweractivate_2-1670905985586.png

I get both Records in the Gallery I expected now, and B

 

The reason it works is because I first split the string containing all of the strings in it, into individual strings without the commas. 

Split(Listing,",")
This makes a Table. 

Next, I use the LookUp function, but rather than a whole data source or collection I just use the Table itself that was Split as the input table, using the As operator to name each individual element of the Split(Listing,",") Table as the name of my choosing, ThisListing.

 

So I have:

 

LookUp(Split(Listing,",") As ThisListing, ThisListing.Result in ComboBox1.SelectedItems)

 

Basically I say - From the outer filter, I have the column Listing accessible to each Record. Now take each comma separated Listing in the Listing column (that is a single string at the moment), and give me a Table of individual Listings (strings) instead, each string being a row of a Table and without the commas - that's what Split(Listing,",") does. Now take that Table, and LookUp for me , using each individual Listing itself as a convenience inner element called "ThisListing", and using something called Result that's inside it (this has to do with what Split did with the strings - each one of those individual strings without the comma, ends up as an individual row of a Table, in a single column called Result - that's why it's ThisListing.Result) - with each of these elements called "ThisListing.Result", check if it's contained inside of ComboBox1.SelectedItems.

 

This LookUp will either return one record (Not Blank) or no records (Blank)

Now I want to simply know if it's Blank or Not Blank, because I want to reduce the whole second argument of Filter to just true or false, which is what the outer Filter is actually looking for,  so that's why I use the IsBlank function wrapped around it. I've inverted it intentionally to !IsBlank

So if it is not blank it's true - if it is blank it's false

In other words, not blank means the LookUp returned one record - so it means that one of the individual components (not the whole comma separated string but one specific part of it as you want) has matched one of the ComboBox Selected Items - we want that situation included in the returned Records of the Filter so we want to check if it's not blank and if so, we want it included (true) - otherwise, if there's no match, we want it to return false meaning the LookUp returned no record, and so there was no match at all, and so it should not be included, but should be excluded from the Filter instead.

 

Does it make sense now @JScherff ?

 

Your Scenario

 

So @JScherff - in your specific scenario, I'd recommend something like this:

 

Rewrite your formula of

(IsBlank(cboLLRWho.Selected.Result) || Who in cboLLRWho.SelectedItems),

to something like the below instead:

 

//do something like this instead
(
       IsBlank(cboLLRWho.Selected.Result) 
   || !IsBlank
       (
           LookUp
           (
               Split(Who,", ") As IndividualWho
              ,IndividualWho.Result in cboLLRWho.SelectedItems
           )
       )
),

 

I have intentionally put a space after the comma for your scenario because it may not work without the space. Your examples of multiple departments seem to be separated by both a comma and a single space, rather than just a comma like in my example, that's why I use Split(Who,", ")

 

See if it helps @JScherff 

 

P.S.: I have intentionally avoided the use of the ForAll function here. (Try to avoid using ForAll for just its convenience of looping over things and for no other reason, especially if you try to use it just to loop over something but won't be using the output table of ForAll in any way. Even if it may "work", it's probably going to perform less efficiently that way, and it is not a good practice or habit to get into. In my case, if I had used a ForAll in this scenario, I would probably not have used the output table of ForAll at all, so I avoided using ForAll here. It may be tempting to use ForAll here, but it is better not to use it - so that's why I have not used it here).

THANK YOU!  This was SUPER helpful.  I actually came across the "Split" function right before I saw that I had a reply here, so I think I was finally started in the right direction.  I really appreciate all the time you took to explain this in detail and to format the "fix" into my specific code/application.  

Thank you @poweractivate  for your detailed explanation, I finally managed to resolved the issue 🙂

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27     Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Top Solution Authors
Top Kudoed Authors
Users online (1,984)