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

Power gallery Filtering Based On Option Set value

Hello all need help with below,
I have a gallery (Gallery3) on Screen1, whose Items property is set to
SegmentCollection. The collection is populated using the following formula:

ClearCollect( SegmentCollection, { SegmentName: "All Segment" }, { SegmentName: "Segment 1" }, { SegmentName: "Segment 2" }, { SegmentName: "Segment 3 }, { SegmentName: "Segment 4" } );

On Screen2, I have another gallery (Gallery2_11). The Items property of this gallery is set to the 'Segments' table, which contains a choice column named 'Supporting Segment'. I want to filter Gallery2_11 based on the 'Supporting Segment' selected in Power Apps.

'Supporting Segment' have, Segment 1, Segment 2, Segment 3, and Segment 4 as choices and All segment is not there in choices, but if user select All segment Then gallery will show All records.
and choice is coming from Choices(Segment) in Dataverse

Filter(
Segments,
'Supporting Segment'= Gallery3.Selected.SegmentName
)

when i am filtering on that i am facing error of Incompatible type of comparison , these types cant be compared, table text.
@ShaheerAhmad @WarrenBelz @LaurensM @mmbr1606 @SpongYe 

1 ACCEPTED SOLUTION

Accepted Solutions

Hi @faruk1,

 

The provided code does not seem to throw any errors in my editor. Although I am not a fan of using If statements within the items property - would it be possible to try the code below to see whether splitting the choice & all segment logic affects the errors?

 

If(
    Gallery3.Selected.SegmentName = "All Segment",
    //Apply no filter when all segments is selected
    Segments,
    With(
        {
            //Map gallery selection to correct choice value
            //(Solves the record schema issue)
            wChoice: Switch(
                Gallery3.Selected.SegmentName,
                //Adjust choice name / choice value if necessary
                "Segment 1",
                Segment.'Segment 1',
                "Segment 2",
                Segment.'Segment 2',
                "Segment 3",
                Segment.'Segment 3',
                "Segment 4",
                Segment.'Segment 4'
            )
        },
        Filter(
            Segments,
            //('in' solves the incompatible type issue, table - record)
            wChoice in 'Supporting Segment'
        )
    )
)

 

That said, I usually filter by using a combobox on the same screen without adding additional choice options to display all records. By using a combobox we can show no selection by default which acts similar to our 'All Segments' - when the user selects a selection within the combobox then we apply the filter:

 

//Combobox items property
Choices(Segment)

 

//Gallery items property
Filter(
    Segments,
    !IsBlank(Combobox.Selected) || 'Supporting Segment' = Combobox.Selected
)

 

I hope this helps!

View solution in original post

10 REPLIES 10

Hey @faruk1 

 

You can try this:

Filter(

    Collprospects,

    'Supporting Segment'.Value = Gallery3.Selected.SegmentName

)

 

Let me know if my answer helped solving your issue.

If it did please accept as solution and give it a thumbs up so we can help others in the community.



Greetings

faruk1_0-1710097785896.pngfaruk1_1-1710097819235.png

facing same issue with above formula as well

faruk1_0-1710098999077.png

i am sharing more information about column type and choices

Hi @faruk1,

 

The current error occurs due to the selected gallery item not being the same type (record) as your column (table). Additionally, the collection will not match the expected record schema of your choice set.

 

In order to solve the issue, we will have to (1) map the selected gallery record with the correct choice option to match the Dataverse choice record schema and (2) use the 'in' operator to search whether the currently selected record exists in the multi-select column (table). I recently solved a similar issue here that can provide additional insights - although the column in that post was a single-select choice.

 

With(
    {
        //Map gallery selection to correct choice value
        //(Solves the record schema issue)
        wChoice: Switch(
            Gallery3.Selected.SegmentName,
            //Adjust choice name / choice value if necessary
            "Segment 1",
            Segment.'Segment 1',
            "Segment 2",
            Segment.'Segment 2',
            "Segment 3",
            Segment.'Segment 3',
            "Segment 4",
            Segment.'Segment 4'
        )
    },
    Filter(
        Segments,
        //Filter based on choice if 'All Segment' is not selected
        //('in' solves the incompatible type issue, table - record)
        Gallery3.Selected.SegmentName = "All Segment" || wChoice in 'Supporting Segment'
    )
)

Please note that this approach results in a non-delegable query.

 

As an optimization: Due to Gallery 3 being on another screen than the current gallery, I would recommend saving the selection to a variable and referencing this in your Filter instead.

Navigate(Screen2, ScreenTransition.None, {locSelectedSegment: Gallery3.Selected.SegmentName})

 

If this solves your question, would you be so kind as to accept it as a solution & give it a thumbs up.

Thanks!

thanks @LaurensM , for giving the solution, however it's working for all segments only for other it's not working  for other segments

faruk1_0-1710104045944.png

 

however when i added choices to my gallery which has only Segment1,Segment2,Segment3,Segment4 then below code works fine, but what should i do with all segment?
Filter(
Prospects,
Gallery3.Selected.Value in 'Supporting Segment'.Value
)

Hi @faruk1,

 

I unfortunately am unable to recreate that error on my end. Can you confirm that (1) the code does not provide any errors when written in the Items property, (2) all needed segments are correctly defined within the Switch statement?

 

I hope this helps!

faruk1_0-1710106141861.png

this is the error message i am facing now.  the code does not provide any errors, but my gallery is not filtering based onthat, sometime same items for all segment 

JSON parsing error, the length of option set values does not match the length of option set labels.

Hi @faruk1,

 

The provided code does not seem to throw any errors in my editor. Although I am not a fan of using If statements within the items property - would it be possible to try the code below to see whether splitting the choice & all segment logic affects the errors?

 

If(
    Gallery3.Selected.SegmentName = "All Segment",
    //Apply no filter when all segments is selected
    Segments,
    With(
        {
            //Map gallery selection to correct choice value
            //(Solves the record schema issue)
            wChoice: Switch(
                Gallery3.Selected.SegmentName,
                //Adjust choice name / choice value if necessary
                "Segment 1",
                Segment.'Segment 1',
                "Segment 2",
                Segment.'Segment 2',
                "Segment 3",
                Segment.'Segment 3',
                "Segment 4",
                Segment.'Segment 4'
            )
        },
        Filter(
            Segments,
            //('in' solves the incompatible type issue, table - record)
            wChoice in 'Supporting Segment'
        )
    )
)

 

That said, I usually filter by using a combobox on the same screen without adding additional choice options to display all records. By using a combobox we can show no selection by default which acts similar to our 'All Segments' - when the user selects a selection within the combobox then we apply the filter:

 

//Combobox items property
Choices(Segment)

 

//Gallery items property
Filter(
    Segments,
    !IsBlank(Combobox.Selected) || 'Supporting Segment' = Combobox.Selected
)

 

I hope this helps!

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

Users online (2,072)