cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
HansHeintz
Post Prodigy
Post Prodigy

How have nested gallery items access parent item properties

I have a gallery based on a ParentCollection where each item contains a ChildCollection (added with AddColumns) shown in a subgallery. ParentCollection has a column "Expand" with value set to false to start.
In the parent gallery item I want to hit an "expand" icon that changes the "Expand" property of the parent item and also behavior of the child gallery items.

F.e. I would like to have a label on the childitems with height set to (pseudo syntax)
If(Parent(ThisItem).Expand;60;40)

What syntax would I use?

 

Also when populating the collections I might also add a column expand to the childitems and when hitting the icon on the parent gallery item I might set all childitems to expand:true
When I try this using
ForAll(ThisItem.ChildCollection;{Expand : !Expand}) or
ForAll(ThisItem.ChildCollection;{Expand : true})
Nothing happens. Syntax and names are ok since I get no errors. But nothing happens. Renaming the expand column of the childitems to assure disambiguation ..  no difference.
How would I syntax that approach?


1 ACCEPTED SOLUTION

Accepted Solutions

@HansHeintz 

Okay, so translating this from the sample app I gave you to what you have...

Somewhere in your app you have this formula on an OnSelect action (in mine it was the Load Data button):

ClearCollect(
    KennelDieren8;
    AddColumns(KennelDieren9;
      "Events"; 
         AddColumns(Filter(DierEvent;
                    DocaDierId=dier_id &&
                   (EventtypeId=3 || PlanStatus=0)
                    );
               "rProduct"; Produkt;    
               "EventExpand"; false
                     );
      "DocaDierNr";dier_id;
      "Expand";false                             
   )
)

 

I would change that to the following (as you don't need the EventExpand field in the sub table:

ClearCollect(
    KennelDieren8;
    AddColumns(KennelDieren9;
      "Events"; 
         AddColumns(Filter(DierEvent;
                    DocaDierId=dier_id &&
                   (EventtypeId=3 || PlanStatus=0)
                    );
               "rProduct"; Produkt;    
                     );
      "DocaDierNr";dier_id;
      "Expand";false                             
   )
)

 

 

The Gallery (the outermost) of your app would have this as its Items property (in mine it was on Gallery1):

KennelDieren8

 Your Inner/nested gallery would have a formula on the Items property like this:

AddColumns(ThisItem.Events; "Expanded"; ThisItem.Expand)

Your Icon for expand or colapse would have this in the OnSelect action:

UpdateIf(KennelDieren8; DocaDierNr=ThisItem.DocaDierNr, {Expand:!Expand})

Your Nested gallery will now have a ThisItem.Expand that will change based on the user click of the expand/collapse button.

This should all work for you.

 

Now, to expand (no pun intended) on the statements that you made...

A collection is a "snapshot" in time.  Just like a variable.  If you want to change it, you have a couple of options available.  BUT, when you start doing sub items (i.e. sub tables), you have more steps to go through. 

The advantage of the AddColumns is that it creates a calculated column in your Collection.  So, if you change something about the primary columns, the calculation will reoccur - without you having to re-collect (i.e. take another snapshot).

So, if we can use that mechanism to alter the values, then it is easy.

Otherwise, we have to redo the sub table and update/patch that column in the primary table.  Its a lot of hasle - add columns with a calculated is a breeze.

You would have to do something like this - Do a ForAll or UpdateIf and then use the output of that to update/patch the original table.  Again, a lot of hassle.

 

In the example above, you are using the outermost Expand column to pass the calculated column to the child.  You are doing this on the Items property of the nested gallery.  This will reevaluate whenever there is a change to it.  So...you don't need to do anything else, just let PowerApps do its thing.

 

I hope that is clear for you...If not, just let me know and I can provide more detail.

 

 

 

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

View solution in original post

5 REPLIES 5
RandyHayes
Super User
Super User

@HansHeintz 

So, the issue in the ForAll is that you are actually not doing anything in it...

What you might envision as actually setting the Expand property in the collection is not what is going on.  What it is doing is returning a table of records with an Expand field based on the expand property of your existing collection - that will not do anything for you (especially since you are not assigning it to anything).

In PowerApps, you can't alter values in that way.  The approach is to have your controls change their behavior based on the data.

So, in this case, you need to pass the Expand property of the parent to the child as part of the records. 

This can easily be done with AddColumns(ThisItem.childItems, "Expanded", ThisItem.Expand)

Now every record in the sub gallery will have the parent expand property.  When you change the parent Expand property (through your icon), the sub gallery items will have the proper value of the Expand.

 

Kind of hard to explain, so I've attached a quick sample app to this post.  Download it to your computer, then open PowerApps and either create a blank app or open an existing one.  Then once in the design, go to File->Open->Browse and choose the file you downloaded.

It's a simple Gallery with sub gallery.  The parent has an expand icon and the child gallery "Reacts" to the expand condition.

 

I hope this is helpful for you.

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

Mmm not entirely clear to me yet.

Underneath is the exact code where a collection is added as a column for each item of an existing collection as part of the onselect code of a button.

I cannot place your code in there because clearcollect does not recognize "thisitem".
If I put your code
AddColumns(ThisItem.childItems, "Expanded", ThisItem.Expand)
or in my case AddColumns(ThisItem.Events, "EventExpand", ThisItem.Expand)
in the onselect code of the expand icon at the most the childitems of thisitem know this column but in practice the column "Expanded" does not compute anywhere.

Also I do not know why it would be impossible to change the values for a column in the childitems, be it as I tried before or by some patch construction or by 
UpdateIf(ThisItem.Events;true;{EventExpand:true})
which does not work either.

 

 

;;ClearCollect(
               KennelDieren8            
               ;AddColumns(KennelDieren9
                          ;"Events";AddColumns(
                                                Filter(
                                                                DierEvent
                                                                ;DocaDierId=dier_id And ((EventtypeId=3) Or (PlanStatus=0))
                                                        )
                                                ;"rProduct";Produkt    
                                               ;"EventExpand";false
                                               )         
                          ;"DocaDierNr";dier_id 
                          ;"Expand";false                             
                           )
)

 

 

@HansHeintz 

Okay, so translating this from the sample app I gave you to what you have...

Somewhere in your app you have this formula on an OnSelect action (in mine it was the Load Data button):

ClearCollect(
    KennelDieren8;
    AddColumns(KennelDieren9;
      "Events"; 
         AddColumns(Filter(DierEvent;
                    DocaDierId=dier_id &&
                   (EventtypeId=3 || PlanStatus=0)
                    );
               "rProduct"; Produkt;    
               "EventExpand"; false
                     );
      "DocaDierNr";dier_id;
      "Expand";false                             
   )
)

 

I would change that to the following (as you don't need the EventExpand field in the sub table:

ClearCollect(
    KennelDieren8;
    AddColumns(KennelDieren9;
      "Events"; 
         AddColumns(Filter(DierEvent;
                    DocaDierId=dier_id &&
                   (EventtypeId=3 || PlanStatus=0)
                    );
               "rProduct"; Produkt;    
                     );
      "DocaDierNr";dier_id;
      "Expand";false                             
   )
)

 

 

The Gallery (the outermost) of your app would have this as its Items property (in mine it was on Gallery1):

KennelDieren8

 Your Inner/nested gallery would have a formula on the Items property like this:

AddColumns(ThisItem.Events; "Expanded"; ThisItem.Expand)

Your Icon for expand or colapse would have this in the OnSelect action:

UpdateIf(KennelDieren8; DocaDierNr=ThisItem.DocaDierNr, {Expand:!Expand})

Your Nested gallery will now have a ThisItem.Expand that will change based on the user click of the expand/collapse button.

This should all work for you.

 

Now, to expand (no pun intended) on the statements that you made...

A collection is a "snapshot" in time.  Just like a variable.  If you want to change it, you have a couple of options available.  BUT, when you start doing sub items (i.e. sub tables), you have more steps to go through. 

The advantage of the AddColumns is that it creates a calculated column in your Collection.  So, if you change something about the primary columns, the calculation will reoccur - without you having to re-collect (i.e. take another snapshot).

So, if we can use that mechanism to alter the values, then it is easy.

Otherwise, we have to redo the sub table and update/patch that column in the primary table.  Its a lot of hasle - add columns with a calculated is a breeze.

You would have to do something like this - Do a ForAll or UpdateIf and then use the output of that to update/patch the original table.  Again, a lot of hassle.

 

In the example above, you are using the outermost Expand column to pass the calculated column to the child.  You are doing this on the Items property of the nested gallery.  This will reevaluate whenever there is a change to it.  So...you don't need to do anything else, just let PowerApps do its thing.

 

I hope that is clear for you...If not, just let me know and I can provide more detail.

 

 

 

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

Thnx! That worked for me

BTW to set the collaps column of the parent item I CAN do (in the onselect of an icon on the parent item)

UpdateIf(KennelDieren;true;{Expand : false})
;;Patch(KennelDieren;ThisItem;{Expand : !Expand})

 

@HansHeintz 

Good deal!

Yes, your formula will result in all of the other currently expanded sections to collapse (not expand) and the one you are on (ThisItem) to be expanded.  Although the !Expand in the formula is ambiguous as the only real value at that point would be true, since you, in the previous line of the formula, had already set them all to false.

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

Helpful resources

Announcements

Update! June 13th, Community Ambassador Call for User Group Leaders and Super Users

Calling all Super Users & User Group Leaders     UPDATE:  We just wrapped up June's Community Ambassador monthly calls for Super Users and User Group Leaders. We had a fantastic call with lots of engagement. We are excited to share some highlights with you!    Big THANK YOU to our special guest Thomas Verhasselt, from the Copilot Studio Product Team for sharing how to use Power Platform Templates to achieve next generation growth.     A few key takeaways: Copilot Studio Cookbook Challenge:  Week 1 results are posted, Keep up the great work!Summer of Solutions:  Starting on Monday, June 17th. Just by providing solutions in the community, you can be entered to win tickets to Power Platform Community Conference.Super User Season 2: Coming SoonAll communities moving to the new platform end of July We also honored two different community members during the call, Mohamed Amine Mahmoudi and Markus Franz! We are thankful for both leaders' contributions and engagement with their respective communities. 🎉   Be sure to mark your calendars and register for the meeting on July 11th and stay up to date on all of the changes that are coming. Check out the Super User Forum boards for details.   We're excited to connect with you and continue building a stronger community together.   See you at the call!  

Win free tickets to the Power Platform Conference | Summer of Solutions

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**

Copilot Cookbook Challenge | Week 2 Results | Win Tickets to the Power Platform Conference

We are excited to announce the "The Copilot Cookbook Community Challenge is a great way to showcase your creativity and connect with others. Plus, you could win tickets to the Power Platform Community Conference in Las Vegas in September 2024 as an amazing bonus.   Two ways to enter: 1. Copilot Studio Cookbook Gallery: https://aka.ms/CS_Copilot_Cookbook_Challenge 2. Power Apps Copilot Cookbook Gallery: https://aka.ms/PA_Copilot_Cookbook_Challenge   There will be 5 chances to qualify for the final drawing: Early Bird Entries: March 1 - June 2Week 1: June 3 - June 9Week 2: June 10 - June 16Week 3: June 17 - June 23Week 4: June 24 - June 30     At the end of each week, we will draw 5 random names from every user who has posted a qualifying Copilot Studio template, sample or demo in the Copilot Studio Cookbook or a qualifying Power Apps Copilot sample or demo in the Power Apps Copilot Cookbook. Users who are not drawn in a given week will be added to the pool for the next week. Users can qualify more than once, but no more than once per week. Four winners will be drawn at random from the total qualifying entrants. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once. If they are drawn multiple times, another user will be drawn at random. Prizes:  One Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value, does not include travel, lodging, or any other expenses) Winners are also eligible to do a 10-minute presentation of their demo or solution in a community solutions showcase at the event. To qualify for the drawing, templates, samples or demos must be related to Copilot Studio or a Copilot feature of Power Apps, Power Automate, or Power Pages, and must demonstrate or solve a complete unique and useful business or technical problem. Power Automate and Power Pagers posts should be added to the Power Apps Cookbook. Final determination of qualifying entries is at the sole discretion of Microsoft. Weekly updates and the Final random winners will be posted in the News & Announcements section in the communities on July 29th, 2024. Did you submit entries early?  Early Bird Entries March 1 - June 2:  If you posted something in the "early bird" time frame complete this form: https://aka.ms/Copilot_Challenge_EarlyBirds if you would like to be entered in the 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. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1.  @Mathieu_Paris 1.   @SpongYe 2.  @Dhanush 2.   @Deenuji 3.  n/a3.   @Nived_Nambiar  4.  n/a4.   @ManishSolanki 5.  n/a5.    n/a   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. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1. Kasun_Pathirana1. ManishSolanki2. cloudatica2. madlad3. n/a3. SpongYe4. n/a4. n/a5. n/a5. n/a

Celebrating the June Super User of the Month: Markus Franz

Markus Franz is a phenomenal contributor to the Power Apps Community. Super Users like Markus inspire others through their example, encouragement, and active participation.    The Why: "I do this to help others achieve what they are trying to do. As a total beginner back then without IT background I know how overwhelming things can be, so I decided to jump in and help others. I also do this to keep progressing and learning myself." Thank you, Markus Franz, for your outstanding work! Keep inspiring others and making a difference in the community! 🎉  Keep up the fantastic work! 👏👏   Markus Franz | LinkedIn  Power Apps: mmbr1606  

Your Moment to Shine: 2024 PPCC’s Got Power Awards Show

For the third year, we invite you, our talented community members, to participate in the grand 2024 Power Platform Community Conference's Got Power Awards. This event is your opportunity to showcase solutions that make a significant business impact, highlight extensive use of Power Platform products, demonstrate good governance, or tell an inspirational story. Share your success stories, inspire your peers, and show off some hidden talents.  This is your time to shine and bring your creations into the spotlight!  Make your mark, inspire others and leave a lasting impression. Sign up today for a chance to showcase your solution and win the coveted 2024 PPCC’s Got Power Award. This year we have three categories for you to participate in: Technical Solution Demo, Storytelling, and Hidden Talent.      The Technical solution demo category showcases your applications, automated workflows, copilot agentic experiences, web pages, AI capabilities, dashboards, and/or more. We want to see your most impactful Power Platform solutions!  The Storytelling category is where you can share your inspiring story, and the Hidden Talent category is where your talents (such as singing, dancing, jump roping, etc.) can shine! Submission Details:  Fill out the submission form https://aka.ms/PPCCGotPowerSignup by July 12th with details and a 2–5-minute video showcasing your Solution impact. (Please let us know you're coming to PPCC, too!)After review by a panel of Microsoft judges, the top storytellers will be invited to present a virtual demo presentation to the judges during early August. You’ll be notified soon after if you have been selected as a finalist to share your story live at PPCC’s Got Power!  The live show will feature the solution demos and storytelling talents of the top contestants, winner announcements, and the opportunity to network with your community.  It's not just a showcase for technical talent and storytelling showmanship, show it's a golden opportunity to make connections and celebrate our Community together! Let's make this a memorable event! See you there!   Mark your calendars! Date and Time: Thursday, Sept 19th Location: PPCC24 at the MGM Grand, Las Vegas, NV 

Tuesday Tip | Accepting Solutions

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   To enhance our collaborative environment, it's important to acknowledge when your question has been answered satisfactorily. Here's a quick guide on how to accept a solution to your questions: Find the Helpful Reply: Navigate to the reply that has effectively answered your question.Accept as Solution: Look for the "Accept as Solution" button or link, usually located at the bottom of the reply.Confirm Your Selection: Clicking this button may prompt you for confirmation. Go ahead and confirm that this is indeed the solution.Acknowledgment: Once accepted, the reply will be highlighted, and the original post will be marked as "Solved". This helps other community members find the same solution quickly. By marking a reply as an accepted solution, you not only thank the person who helped you but also make it easier for others with similar questions to find answers. Let's continue to support each other by recognizing helpful contributions. 

Top Solution Authors
Top Kudoed Authors
Users online (3,840)