cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
PhiReMan
Frequent Visitor

toggle in gallery

I have a gallery that displays values from a SharePoint list. The behavior I want to achieve is as follows:
  1. When a user checks Toggle1, Toggle2 should be set to DisplayMode.Disabled.
  2. Conversely, when a user checks Toggle2, Toggle1 should be set to DisplayMode.Disabled.

Here’s what I’ve implemented:

  • In Toggle2.DisplayMode: "If(Toggle1.Value=true;DisplayMode.Disabled;DisplayMode.Edit)"
  • In Toggle1.DisplayMode: "If(Toggle2.Value=true;DisplayMode.Disabled;DisplayMode.Edit)"

When I test this in Play Mode by checking Toggle1 for the first item in the gallery, I get the following results:

  • Toggle2 for Item 1 of the gallery is correctly disabled.
  • Toggle2 for Items 2 and 3 of the gallery are still in Edit Mode (as expected).
  • Problem: Toggle2 for all other items in the gallery are disabled, but they should also be in Edit Mode.

Surprising Behavior:

If I reload the site and only check Toggle1, the same issue persists.

However, if I reload the site and first scroll down a few items and then go back up to check Toggle1 for item 1 of the gallery, then all the toggles for the items I scrolled to remain in Edit Mode, while the toggles for the items I did not scroll to are disabled.

 

(By the way: Actually, I want to use a Patch function when using the toggle. However, the same behavior occurs there: When I check the toggle for item 1, all toggles for all items that I did not scroll to also become checked, and SharePoint registers entries as if the user had checked all those toggles for all those items.)

 

Glad if somebody is able to find a solution.

5 REPLIES 5
Pstork1
Most Valuable Professional
Most Valuable Professional

If you aren't tracking the value of Toggle1 and Toggle2 in the data source then the value for each Toggle will be the same for every record in the gallery. You are repeating the same control. I'm not sure why toggle2 is staying in Edit mode for items 2 and 3. It should be disabled in all records after disabling in the first. If you are tracking the value in the list then you need to use thisItem.column to set Edit or disabled. That will tie it to the individual item.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
PhiReMan
Frequent Visitor

I’m uncertain if I understand you correctly:

 

Are you suggesting that all the toggles in every item of a gallery should behave uniformly? In other words, if I check one toggle in a specific gallery item, should all toggles across all items in the gallery also get checked? This doesn’t align with my previous experiences—I’ve used the same functionality in other apps, and it worked correctly.

 

Regarding your mention of ‘tracking the value of Toggle 1 in the datasource,’ could you clarify? Are you suggesting that I create a new column (perhaps named ‘Toggles’) in my SharePoint list, which feeds the gallery? However, this approach might not be feasible because the toggles depend not only on the entries in the SharePoint list but also on individual users.

Alternatively, I could create a new datasource containing all possible combinations of users and SharePoint list entries to store toggle values. However, this seems like a significant effort for something that has worked seamlessly in my other apps.

Pstork1
Most Valuable Professional
Most Valuable Professional

Not quite. I am suggesting that if you add one toggle control to the gallery template, that will add the same toggle control to each record in the gallery. For that one toggle control they will all be tied together unless you link them to something in the data source behind the gallery.  If you don't do that then when you toggle the control in the first gallery item, it will be reflected in all the rest.  To avoid this you need to have a field in the data source that is tied to the value of the control. That way it can have a different value for each record. That is the way its designed to work.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
Pstork1
Most Valuable Professional
Most Valuable Professional

OK, I just did some testing and you are correct. Its been a while since I tried this and it never used to work this way. I still can't explain what you are seeing.  In my test the display modes for each set of toggles in the record operate as you expect them to.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
PhiReMan
Frequent Visitor

I was able to create a workaround for the problem. Below are the details. But let me first describe another way the problem manifests:

Given the following:

  • a SharePoint list ("Test") with 20 entries.
  • a Gallery referencing this list. The template is large, showing only the first item of the Gallery practically. Therefore, scrolling down is necessary to see the other 19 items.
  • a Toggle in the Gallery's template.
  • a Label in the Gallery's template displaying Text=Toggle1.Value.

When the Toggle in the first Gallery item is set to true, its Label shows true (as expected). While scrolling down, the following two Labels show false (as expected because their Toglle has not been set to true). However, all other Labels in the remaining 17 items display true, despite the adjacent Toggle being set to false.

However, if one scrolls to the bottom after starting the app and then back up, and only then sets the Toggle in Item 1 to true, only the first Label shows true, while all others display false. In this case, the app behaves as expected.

 

So, my workaround looks like this: In the OnChange property of the Toggle, I create a context variable storing the ID of the item located at the bottom of the Gallery that was edited:

If(ThisItem.ID > MaxId, UpdateContext({MaxId: ThisItem.ID}), false)

This way, the app knows how far down the user has scrolled at least. In the Label's text, I write:

If(ThisItem.ID <= MaxId, Toggle1.Value, false)

This means that only the Labels in the items that the user has scrolled to will display the value of their Toggle. All other Labels show false because the user hasn't scrolled down to those yet.

Perhaps you might have a better solution in mind?

Thank you for the support.

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,365)