cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
RMDNA
Helper III
Helper III

Updateif button for all gallery items

Hi all, just a couple questions about gallery interactions.

 

Question 1:

I have a bunch of items in a gallery from one of my collections. Each item has a button with an updateif OnSelect to update that record's status. What I'd like to do is add another button, outside the gallery, that runs the same operation for all items currently in the gallery. 

 

Data source is Dataverse, Gallery is galWeeklyTimeEntries, Collection is ColWeeklyTimeEntries, button OnSelect is:

 

 

UpdateIf('Project Approval', 'Time Entry'.'GUID' in ThisItem.AllGUIDs, {'Record Stage': 'Record Stage (Project Approval)'.Approved});

 

 

The gallery items are aggregations of individual entries, so the button is taking all the GUIDs for all those entries and changing their status. I thought about changing ThisItem.AllGUID to galWeeklyTimeEntries.AllGUID, but that apparently doesn't reference the individual items.

 

RMDNA_0-1617983039008.png

 

Question 2:

If that's possible, I'd also like the option to "Approve All", but only for items that have been checked via a checkbox in the gallery. Also doable?

 

RMDNA_0-1617983619145.png

Thanks!

1 ACCEPTED SOLUTION

Accepted Solutions

@RMDNA 

So in general, you've essentially over complicated the process.  You really don't need a collection for anything except in a scenario where you are going to need the ability to add or remove rows (an in-app database).  So your Items property can just be the formula that you are otherwise having to collect through a behavioral action.

If you use a collection, your Gallery will not be dynamic - in other words, you would need to recollect the collection in order for your Gallery to show the changes.  If you skip the collections and just use the formula straight on the Items property, your Gallery will be dynamic and reflect the changes immediately without a performance-costly recollection of all the data.  

You stated you did this to avoid delegation issues, but the reality is, your collection formula will have all the same delegation issues.  AddColumns, GroupBy and ShowColumns are not delegable no matter where you use them. The formula can be made to be delegable - but let's table that as a separate topic for the moment.

 

What I am seeing is that you are not embracing the records you are grouping by in "Other".  Other (as you defined it) is going to have all the records in it for the group.  So, there is no need to concat ID's together to keep track of them...they are already there.

 

I am not entirely clear in your formula why you are double grouping and what your real grouping needed is supposed to be.

 

But at any rate, your button IN the gallery for updating should be something along this line:

Patch('Project Approval',
    ForAll(ThisItem.Other As _item,
        {'Project Approval': _item.mydyn_timeentry,
         'Record Stage': 'Record Stage (Project Approval)'.Approved
        }
    )
)

 

Outside of the Gallery for the all items in the Gallery with a check box checked.

Patch('Project Approval',
    ForAll(Ungroup(Filter(yourGallery.AllItems, theCheckBox.Value), "Other") As _item,
        {'Project Approval': _item.mydyn_timeentry,
         'Record Stage': 'Record Stage (Project Approval)'.Approved
        }
    )
)

   

You will notice in the above formulas that you are actually utilizing the underlying grouped records, because those are the ones you want.  Trying to keep track of their GUID's is not relevant because they are already there.

 

Hopefully that makes some sense.

Keep in mind, that some of the above is theoretical because we'd really need to address that items/collection formula to make sure that you are getting what you need in the records.  I am concerned that you used "Other" in both groupby functions and that you are double grouping.  I don't believe you need to do any of that.  And certainly not dropping the columns (as you are with the ShowColumns).

_____________________________________________________________________________________
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

14 REPLIES 14

@RMDNA 

Your formula outside of the Gallery should refer to the gallery.

So:

Patch('Project Approval', 
    ForAll(galWeeklyTimeEntries.AllItems As _item,
        {'Time Entry'.'GUID':  _item.'Time Entry'.'GUID', 
         'Record Stage': 'Record Stage (Project Approval)'.Approved
        }
    )
)

 

If you want to do this from CheckBoxes, then the formula would be:

Patch('Project Approval', 
    ForAll(
        Filter(galWeeklyTimeEntries.AllItems, theChekbox.Value) As _item,
        {'Time Entry'.'GUID':  _item.'Time Entry'.'GUID', 
         'Record Stage': 'Record Stage (Project Approval)'.Approved
        }
    )
)

 

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!
RMDNA
Helper III
Helper III

Hi @RandyHayes,

 

I get a few errors when trying to implement your formula:

 

RMDNA_0-1617986160186.png

 

If it helps to clarify, each gallery entry contains the (hidden) column AllGUIDs, which is a comma-separated concat of each underlying entry's GUID, so I can approve them in bulk. Let me know what other info I could provide to assist.

 

Gallery data (GroupBy collection):

 

NameProjectAllGUIDsHours
JaneTime Entry Test 1"abcde","fghij"20


Underlying unaggregated data:

 

NameProjectGUIDHours
JaneTime Entry Test 1abcde10
JaneTime Entry Test 1fghij10

@RMDNA 

So this is vastly different...you have a Gallery that is showing grouped data and that grouped data has record you want to update.

Is this correct?  I missed that subtle point in your original post.

 

So what you need to do then is to ungroup the items in your formula.

This is going to take a few answers to some questions.

1) What is the items property of your Gallery?  If for some reason you have this based on a collection, what is the definition (how do you set) the collection.

2) What are the real names of your columns (specifically - Name and Record Stage)

 

 

 

_____________________________________________________________________________________
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!

Hi @RandyHayes, - sorry for the confusion. I don't expect you to troubleshoot my mess of code, so let me know if this requires too much of an overhaul.

 

I already have a button for each entry in my gallery that will update multiple underlying records at once by comparing its list of aggregated GUIDs to the individual GUIDs in my data source. That part works fine. My goal (which I suppose is more complicated than I expected) is essentially just to trigger all those buttons at once ("Approve All"), without needing to click on each of them individually. 

 

I'm still new to PowerApps, so I'll try to answer your questions the best I can.

 

1. I'm using a collection to power the gallery in an attempt to avoid the giant pile of delegation errors I was getting trying to achieve the same results using a view or the source table. I'd much rather handle the necessary aggregation upstream, but for a variety of reasons, let's assume that's off the table.

 

The formula is below. It takes my unaggregated time entry data (date, user name, project, task, hours, GUID) and rolls it up by day, project, total hours, and concatenated GUIDs. Almost every field in the table is a lookup (since we're dealing with Dynamics 365 data).

 

Spoiler
ClearCollect(
    ColWeeklyTimeEntries,
    AddColumns(
        GroupBy(
            AddColumns(
                GroupBy(
                    ShowColumns(
                        AddColumns(
                            Filter(
                                'Project Approval','Project Approval (Views)'.'Time Entries for Approval',
                                msdyn_date >= VarSelectedStartDate && msdyn_date <= VarSelectedEndDate),
                            "DateString",Text(msdyn_date,ShortDate),
                            "ResourceName",msdyn_bookableresource.Name,
                            "ProjectName",Project.'Project Name',
                            "GUID",'Time Entry'.'Time Entry'
                        ),
                        "DateString","ResourceName","ProjectName","msdyn_ProjectTask","GUID","msdyn_costquantity"
                    ),
                    "DateString","ResourceName","ProjectName","GUID","Other"
                ),
                "DayHours",Sum(Other,msdyn_costquantity),
                "ComboGUID",Concat(Other,GUID & ", ")
            ),
            "ResourceName","ProjectName","Other"
        ),
        "WeekHours",Sum(Other,DayHours),
        "AllGUID",Concat(Other,ComboGUID)
    ))

 

I'm curious about your wording of "If for some reason" - are using collections with galleries bad practice?

 

2. In the backend, 'Record Stage" is actually msdyn_recordstage, "Name" is msdyn_name (surfaced as msdyn_bookableresource.Name), and "GUID" is 'msdyn_timeentry' (surfaced as 'Time Entry'.'Time Entry'). The tables in the dataverse are system-created.

@RMDNA 

So in general, you've essentially over complicated the process.  You really don't need a collection for anything except in a scenario where you are going to need the ability to add or remove rows (an in-app database).  So your Items property can just be the formula that you are otherwise having to collect through a behavioral action.

If you use a collection, your Gallery will not be dynamic - in other words, you would need to recollect the collection in order for your Gallery to show the changes.  If you skip the collections and just use the formula straight on the Items property, your Gallery will be dynamic and reflect the changes immediately without a performance-costly recollection of all the data.  

You stated you did this to avoid delegation issues, but the reality is, your collection formula will have all the same delegation issues.  AddColumns, GroupBy and ShowColumns are not delegable no matter where you use them. The formula can be made to be delegable - but let's table that as a separate topic for the moment.

 

What I am seeing is that you are not embracing the records you are grouping by in "Other".  Other (as you defined it) is going to have all the records in it for the group.  So, there is no need to concat ID's together to keep track of them...they are already there.

 

I am not entirely clear in your formula why you are double grouping and what your real grouping needed is supposed to be.

 

But at any rate, your button IN the gallery for updating should be something along this line:

Patch('Project Approval',
    ForAll(ThisItem.Other As _item,
        {'Project Approval': _item.mydyn_timeentry,
         'Record Stage': 'Record Stage (Project Approval)'.Approved
        }
    )
)

 

Outside of the Gallery for the all items in the Gallery with a check box checked.

Patch('Project Approval',
    ForAll(Ungroup(Filter(yourGallery.AllItems, theCheckBox.Value), "Other") As _item,
        {'Project Approval': _item.mydyn_timeentry,
         'Record Stage': 'Record Stage (Project Approval)'.Approved
        }
    )
)

   

You will notice in the above formulas that you are actually utilizing the underlying grouped records, because those are the ones you want.  Trying to keep track of their GUID's is not relevant because they are already there.

 

Hopefully that makes some sense.

Keep in mind, that some of the above is theoretical because we'd really need to address that items/collection formula to make sure that you are getting what you need in the records.  I am concerned that you used "Other" in both groupby functions and that you are double grouping.  I don't believe you need to do any of that.  And certainly not dropping the columns (as you are with the ShowColumns).

_____________________________________________________________________________________
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!
RMDNA
Helper III
Helper III

@RandyHayes - to be honest, I'm not entirely clear on what I'm doing either. I'm on my second week of learning PowerApps, and I've been able to get most things to work through experimentation (and certainly luck). I'll keep working my way through the documentation and your answers. Thanks for the help! 

Hi @RandyHayes,

 

Taking your advice, I completely rewrote the gallery code to avoid collections and pull data directly from the table. It's much simpler now - there's no more double-grouping or column dropping, so thanks for the insights there.

 

The only issue I'm running into now is the Patch() formula for the Approve Selected button. I'm getting an "Invalid argument type (Table). Expecting a Record value instead" error.

 

 

Patch('Project Approval',
    ForAll(Ungroup(Filter(galWeeklyTimeEntries.AllItems, cbCheckbox.Value), "Other") As _item,
        {'Project Approval': _item.GUID,
         'Record Stage': 'Record Stage (Project Approval)'.Approved
        }
    )
)

 

 

I confirmed that the ungrouping and checkboxes are working properly - I can select boxes and have the appropriate GUIDs appear in a data table. Any ideas what the issue is?

@RMDNA 

Which part of the formula are you seeing that on?

_____________________________________________________________________________________
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!

Somewhere in Patch, not able to tell specifically - regardless of where I hover over the formula, I get that same message. 

 

RMDNA_1-1618252852749.png

 

 

 

 

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