cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

Gallery stop selecting duplicate item from combobox

Hi All,

 

I'm currently wrestling with same  issue that is driving me nuts!

So I have a gallery where the user can edit entries through a combobox1which has dates [1,2,3,4---------5] and in the same row i have onother combobox2[1,2,3] the second combobox should not show already selected dates if selected it show throw an error notify

once that combobox1 dates have been selected in combobox1 and combobox2 

in the second row combobox it should not show the same dates or should throw an error [Notifying dates have been already selected in the previous row]

. The data is then patched row by row as the user presses the save icon (present on each row) back to a dataverse table

PowerrangerM_0-1672292643100.png

Here shift b shows all days of month [1,2,3,4,5 till end date] if already selected in shift B those dates should not be show in next combobox i.e shift c  and the next row combobox of Shift B like wise i dates already chosen it should not show or throw error 

im storing combobox selected items in collection on change property of combobox  in way comma separated string 1,2,3,4

 

2 ACCEPTED SOLUTIONS

Accepted Solutions

Hi @Anonymous, should the we avoid duplicates within all rows or only avoid row specific duplicates?

 

Let's use an example below (Row 1) :

 

Shift BShift C
1, 2, 34, 5

 

Shift C will not show 1, 2, 3 during selection because they were already taken in Shift B. This Row-level-specific duplication check can easily be done by filtering the Items property of the Shift C combobox:

 

//I used an array of 9 numbers during testing
Filter([1,2,3,4,5,6,7,8,9],!(ThisRecord in ComboBox1.SelectedItems))

 

However, this duplication check will not go across rows. Row 2 Shift B & C will still be able to select 1,2,3,4 & 5 even though they were selected in Row 1.

 

If we want to avoid having duplicates across rows, meaning previously selected numbers in Shift B & C should not show in the item list of rows below. This can be achieved by saving the selected numbers in a collection (OnChange) and filtering the date list by removing all dates that are within the collection (Items property).

 

OnChange of Shift B & C:

 

//Each new selected number will be added to the duplication check collection
ForAll(
    Self.SelectedItems,
    If(
        !(ThisRecord in colSelected),
        Collect(
            colSelected,
            ThisRecord
        )
    )
)

 

Items property of Shift B & C:

 

//This filters out all previously selected numbers
//My test was limited to 9 numbers, replace with your item source
Filter([1,2,3,4,5,6,7,8,9],!(ThisRecord in colSelected))

 

The Items and OnChange logic will make sure that Row 2 does not show 1 up to 5 in the item list for Shift B and C, since they were selected in Row 1. This will ensure that the user cannot select duplicates during initial creation.

 

If they can save it to a collection/table and edit it on a later date, you might want to add the code below to the OnVisible of that screen. Currently the code will not take previously saved numbers into account. The colSelected only gets filled when the ComboBoxes get changed.

 

The code below will load the previously saved numbers to the collection (you mentioned they were saved to a comma-separated string field):

 

//OnVisible of the screen
Clear(colSelected);
ForAll(
    //Replace colSavedSelection with your actual collection or data source
    colSavedSelection,
    ForAll(
        Split(
            //Replace DateString with the field you use to save the selected dates as a comma-separated string
            ThisRecord.DateString,
            ","
        ) As Inner,
        Collect(
            colSelected,
            Value(Inner.Result)
        )
    )
);

 

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

Thanks!

View solution in original post

Hi @Anonymous,

 

I now indeed notice that the solution does not take removed records into account. Thanks for bringing this to my attention. I did some further testing and managed to meet the remove requirement by changing the previous OnChange property code.

 

OnChange of shift B & C:

//Clear the collection
Clear(colSelected);
//Fetch all selected items of all records for both comboboxes
ForAll(
    GalleryName.AllItems,
    Collect(
        colSelected,
        ThisRecord.ShiftBCombobox.SelectedItems,
        ThisRecord.ShiftCCombobox.SelectedItems
    )
)

 

By clearing the collection and fetching all selected items during an OnChange event, we can now keep track of removed items.

 

With app performance in mind, I wanted to avoid having to collect all items during each OnChange in my first solution, but it is needed to keep track of removed items. Performance wise, I did not have any issues in my test app but it might be worth testing in your case.

 

I hope this helps!

View solution in original post

7 REPLIES 7

Hi,

You can just Filter the items that was not selected, like this:

Filter(
    Choices, // replace with your choices
    !(Value in ComboBox.SelectedItems.Value) // replace 'Value' and 'ComboBox' with your components
)

Here is an example:

I create 2 combobox with the same source (Sequence(5))

victorcp_0-1672309889144.png

And for the seccond combobox I created a filter to exclude the selected items of the first combobox

victorcp_3-1672310128525.png

 

victorcp_2-1672310059205.png

 

Any doubts please let me know

Hi @Anonymous, should the we avoid duplicates within all rows or only avoid row specific duplicates?

 

Let's use an example below (Row 1) :

 

Shift BShift C
1, 2, 34, 5

 

Shift C will not show 1, 2, 3 during selection because they were already taken in Shift B. This Row-level-specific duplication check can easily be done by filtering the Items property of the Shift C combobox:

 

//I used an array of 9 numbers during testing
Filter([1,2,3,4,5,6,7,8,9],!(ThisRecord in ComboBox1.SelectedItems))

 

However, this duplication check will not go across rows. Row 2 Shift B & C will still be able to select 1,2,3,4 & 5 even though they were selected in Row 1.

 

If we want to avoid having duplicates across rows, meaning previously selected numbers in Shift B & C should not show in the item list of rows below. This can be achieved by saving the selected numbers in a collection (OnChange) and filtering the date list by removing all dates that are within the collection (Items property).

 

OnChange of Shift B & C:

 

//Each new selected number will be added to the duplication check collection
ForAll(
    Self.SelectedItems,
    If(
        !(ThisRecord in colSelected),
        Collect(
            colSelected,
            ThisRecord
        )
    )
)

 

Items property of Shift B & C:

 

//This filters out all previously selected numbers
//My test was limited to 9 numbers, replace with your item source
Filter([1,2,3,4,5,6,7,8,9],!(ThisRecord in colSelected))

 

The Items and OnChange logic will make sure that Row 2 does not show 1 up to 5 in the item list for Shift B and C, since they were selected in Row 1. This will ensure that the user cannot select duplicates during initial creation.

 

If they can save it to a collection/table and edit it on a later date, you might want to add the code below to the OnVisible of that screen. Currently the code will not take previously saved numbers into account. The colSelected only gets filled when the ComboBoxes get changed.

 

The code below will load the previously saved numbers to the collection (you mentioned they were saved to a comma-separated string field):

 

//OnVisible of the screen
Clear(colSelected);
ForAll(
    //Replace colSavedSelection with your actual collection or data source
    colSavedSelection,
    ForAll(
        Split(
            //Replace DateString with the field you use to save the selected dates as a comma-separated string
            ThisRecord.DateString,
            ","
        ) As Inner,
        Collect(
            colSelected,
            Value(Inner.Result)
        )
    )
);

 

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

Thanks!

Anonymous
Not applicable

Hi @LaurensM 

 

Thanks a lot for the reply

For your question

Hi @PowerrangerM, should the we avoid duplicates within all rows or only avoid row specific duplicates?

Answer :avoid duplicates within all rows 

 

i really appreciate it i  will try the provided steps.

Anonymous
Not applicable

Hi @victorcp 

 

Thanks for taking time and replying 

However the solution doesnt work for all rows as  we should  avoid duplicates within all rows

Anonymous
Not applicable

Hi @LaurensM

Thanks  Lauren for your help ,Whenever we remove date from shift b or shift c combobox it has removed from colselected as well so how to achieve this also can you help here ?

 

Hi @Anonymous,

 

I now indeed notice that the solution does not take removed records into account. Thanks for bringing this to my attention. I did some further testing and managed to meet the remove requirement by changing the previous OnChange property code.

 

OnChange of shift B & C:

//Clear the collection
Clear(colSelected);
//Fetch all selected items of all records for both comboboxes
ForAll(
    GalleryName.AllItems,
    Collect(
        colSelected,
        ThisRecord.ShiftBCombobox.SelectedItems,
        ThisRecord.ShiftCCombobox.SelectedItems
    )
)

 

By clearing the collection and fetching all selected items during an OnChange event, we can now keep track of removed items.

 

With app performance in mind, I wanted to avoid having to collect all items during each OnChange in my first solution, but it is needed to keep track of removed items. Performance wise, I did not have any issues in my test app but it might be worth testing in your case.

 

I hope this helps!

Anonymous
Not applicable

Thanks @LaurensM we implemented the way you suggested it worked ,now we are working on if the time sheet is already been submitted those default selected items should also be not shown in the Combobox dates of both shift b and shift c 

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 (1,290)