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

Patch Gallery Items only with condition

Hi all,

 

Hope you are doing well.

 

I'm blocked since hours and maybe can someone help me here!

 

I have a gallery where user will need to fill 4 or 5 input : Calls Handled, Emails Handled, SL1, SL2, SL3, SL4 (all are numbers input)

 

I want to patch only gallery items with below condition : 

- IF both Calls Handled and Emails Handled are blank then not patch the item.

- IF Calls Handled OR Emails Handled are not blank AND SL1+SL2+SL3+SL4 doesn't equal to Calls Handled + Emails Handled then no patch the item.

 

As per the below photo, only the first item will be patched.

Mts1_0-1659615649731.png

 

 

I don't even know if this requirements is possible or not.

 

Thanks in advance for your help,

 

Regards

 

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

Hey @Anonymous, you are getting close, but think about what we've already done - used ForAll() to iterate over multiple gallery items. So, if you have multiple nested galleries, then perhaps you need another ForAll()? 😉

 

ForAll(
    galParent.AllItems As ParentGallery,
	ForAll(
		Filter(
			AddColumns(
				ChildGallery.AllItems,
				//===Add a column for sum of Calls and Emails
				"CallsAndEmailsSum", Sum(Value(Prod_inptCallsHandled.Text), Value(Prod_inptEmailsHandled.Text)),
				//===Add a column for sum of all SL inputs
				"SLsSum", Sum(Value(Prod_inptSL1.Text), Value(Prod_inptSL2.Text), Value(Prod_inptSL3.Text), Value(Prod_inptSL4.Text))
			),
			//===Perform check: Calls + Emails is greater than zero
			//===Perform check: Calls + Emails = Sum of SL inputs
			CallsAndEmailsSum > 0 && CallsAndEmailsSum = SLsSum
		) As ChildGalleryRecord,
		Patch(PAT_Tracker_AppResults, Defaults(PAT_Tracker_AppResults), 
			{'Task Date': Text(Prod_DatePicker.SelectedDate, "dd/mm/yyyy")},
			{'Agent Name': User().FullName},
			{'Agent EmailAddress': User().Email},
			{'Task Type': Text("Handled")},
			{Country: Prod_DropDown_Country.Selected.Result},
			{Exception: Prod_lblException.Text},
			{Carrier: Prod_lblCarrier.Text},
			{Offered: Value(Prod_lblOffered.Text)},
			{'Calls Handled': If(IsBlank(Prod_inptCallsHandled.Text),0,(Prod_inptCallsHandled.Text))},
			{'Emails Handled': If(IsBlank(Prod_inptEmailsHandled.Text),0,(Prod_inptEmailsHandled.Text))},
			{'Handled SL1': If(IsBlank(Prod_inptSL1.Text),0,(Prod_inptSL1.Text))},
			{'Handled SL2': If(IsBlank(Prod_inptSL2.Text),0,(Prod_inptSL2.Text))},
			{'Handled SL3': If(IsBlank(Prod_inptSL3.Text),0,(Prod_inptSL3.Text))},
			{'Handled SL4': If(IsBlank(Prod_inptSL4.Text),0,(Prod_inptSL4.Text))}
		)
	)
)

View solution in original post

11 REPLIES 11

I'm not sure if you're having trouble with the Filtering of the gallery, or with the Patching, but here is an example:

 

Filtering:

To avoid performing the same Sum() multiple times, I use AddColumns() to name, perform and temporarily store my calculations.

 

Patching:

I am using a ForAll() to set my 'Amount' column, even though it wasn't set in the Gallery. Patching a collection of changes is better described in long form here: https://www.matthewdevaney.com/patch-multiple-records-in-power-apps-10x-faster/ 

 

I am only updating a summary of the Calls + Emails to my 'Amount' field, please see if you can adjust this code to suit your specific needs.

 

metsshan_0-1659621028565.png

metsshan_1-1659621085063.png

 

Patch(
    People,
    ForAll(
        Filter(
            AddColumns(
                galHandled.AllItems,
                "CallsAndEmails", Sum(Value(txtCalls.Text), Value(txtEmails.Text)),
                "TypeSum", Sum(Value(txtSL1.Text), Value(txtSL2.Text), Value(txtSL3.Text), Value(txtSL4.Text))
            ),
            CallsAndEmails > 0 && CallsAndEmails = TypeSum
        ) As GalRecord,
        {
            ID: GalRecord.ID,
            Amount: GalRecord.CallsAndEmails
        }
    )
)

 

 

Edit: if you are CREATING new records with the Patch(), it might look like this:

ForAll(
    Filter(
        AddColumns(
            galHandled.AllItems,
            "CallsAndEmails", Sum(Value(txtCalls.Text), Value(txtEmails.Text)),
            "TypeSum", Sum(Value(txtSL1.Text), Value(txtSL2.Text), Value(txtSL3.Text), Value(txtSL4.Text))
        ),
        CallsAndEmails > 0 && CallsAndEmails = TypeSum
    ) As GalRecord,
    Patch(
        People,
        Defaults(People),
        {
            Title: GalRecord.txtName.Text,
            Amount: GalRecord.CallsAndEmails
        }
    )
)

Hello @Anonymous ,

 

A concept would be 

 

If(
  IsBlank(CallsHandled) && IsBlank(EmailsHandled),
  false,
  If(
   (!IsBlank(CallsHandled) || !IsBlank(EmailsHandled)&&
   (SL1.Text <> CallsHandled || SL1.Text <> EmailsHandled)&&
   (SL2.Text <> CallsHandled || SL2.Text <> EmailsHandled)&&
   (SL3.Text <> CallsHandled || SL3.Text <> EmailsHandled)&& 
   (SL4.Text <> CallsHandled || SL4.Text <> EmailsHandled),
   Patch(
    DATASOURCE,
    Defaults(DATASOURCE),
    {}
   ),
   false
  )
)

 

Not sure if it really works this way. I think you have to adjust the field they check, but the basic code would be this

Anonymous
Not applicable

Hi,

 

A big thank you for your time and your answer.

 

I don't have issue with the patching but with the filtering,

 

I think i can simply my requirement :

 

Here my Sharepoint list

Mts1_0-1659621974496.png

 

I want to patch these inputs - to these Sharepoint Columns : 

inptCallsHandled to Calls Handled

inptEmailsHandled to Emails Handled

inptSL1 to Handled SL1

inptSL2 to Handled SL2

inptSL3 to Handled SL3

inptSL4 to Handled SL4

 

But i want only patch item where 

- ALL Sl's Columns are equal to Calls+Emails HAN

 

 

Based on the below picture, only the fisrt item will be patched 

Mts1_1-1659622571696.png

 

The second will not be patched because SLs are not equal to Handled

The third will not be patched because Calls & Emails are blank. (I think we can based on SL's are blank, if i'm not wrong it's the same)

 

Apologies for my explanations, i know is not really clear

 

Again Thank you

Hi @Anonymous,

 

My filter was doing that, just with different control names. I will rename the fields, annotate it, and you let me know if it works for you?

 

    Filter(
        AddColumns(
            galHandled.AllItems,
            //===Add a columnd for sum of Calls and Emails
            "CallsAndEmails", Sum(Value(inptCallsHandled.Text), Value(inptEmailsHandled.Text)),
            //===Add a columnd for sum of all SL inputs
            "TypeSum", Sum(Value(inputSL1.Text), Value(inputSL2.Text), Value(inputSL3.Text), Value(inputSL4.Text))
        ),
        //===Perform check: Calls + Emails is greater than zero
        //===Perform check: Calls + Emails = Sum of SL inputs
        CallsAndEmails > 0 && CallsAndEmails = TypeSum
    )

 

Anonymous
Not applicable

I adapted your formula with my exact fields names but i have the error "As is not permitted in this context"

 

Below the formula used

 

Filter(
AddColumns(
ChildGallery.AllItems,
//===Add a column for sum of Calls and Emails
"CallsAndEmailsSum", Sum(Value(inptCallsHandled.Text), Value(inptEmailsHandled.Text)),
//===Add a column for sum of all SL inputs
"SLsSum", Sum(Value(inptSL1.Text), Value(inptSL2.Text), Value(inptSL3.Text), Value(inptSL4.Text))
),
//===Perform check: Calls + Emails is greater than zero
//===Perform check: Calls + Emails = Sum of SL inputs
CallsAndEmailsSum > 0 && CallsAndEmailsSum = SLsSum
) As ChildGalleryRecord,

Patch(.............)

"As is not permitted" because the Filter() is not an expression of a parent function. (Read more here)

 

I would recommend either using With() or ForAll(), eg:

ForAll(
    Filter(
        AddColumns(
            ChildGallery.AllItems,
            //===Add a column for sum of Calls and Emails
            "CallsAndEmailsSum", Sum(Value(inptCallsHandled.Text), Value(inptEmailsHandled.Text)),
            //===Add a column for sum of all SL inputs
            "SLsSum", Sum(Value(inptSL1.Text), Value(inptSL2.Text), Value(inptSL3.Text), Value(inptSL4.Text))
        ),
        //===Perform check: Calls + Emails is greater than zero
        //===Perform check: Calls + Emails = Sum of SL inputs
        CallsAndEmailsSum > 0 && CallsAndEmailsSum = SLsSum
    ) As ChildGalleryRecord,

    Patch(.............)
)

 

Anonymous
Not applicable

Hi @metsshan 

 

A big thank you for your reply. 

 

Actually i don't have any error with your formula, but it patch only the child selected item if i'm not wrong. AS you can see on the below photo, 2 items need to be patched. (the number in bracket is the number of items where SLsSum equal to HANsum.

Mts1_0-1659695840052.png

 

So i think the patch work only Child Item where the Parent Gallery is selected. I'm not sure if i'm clear with my explanations, here the code i used.

 

ForAll(
    Filter(
        AddColumns(
            ChildGallery.AllItems,
            //===Add a column for sum of Calls and Emails
            "CallsAndEmailsSum", Sum(Value(Prod_inptCallsHandled.Text), Value(Prod_inptEmailsHandled.Text)),
            //===Add a column for sum of all SL inputs
            "SLsSum", Sum(Value(Prod_inptSL1.Text), Value(Prod_inptSL2.Text), Value(Prod_inptSL3.Text), Value(Prod_inptSL4.Text))
        ),
        //===Perform check: Calls + Emails is greater than zero
        //===Perform check: Calls + Emails = Sum of SL inputs
        CallsAndEmailsSum > 0 && CallsAndEmailsSum = SLsSum
    ) As ChildGalleryRecord,
    Patch(PAT_Tracker_AppResults, Defaults(PAT_Tracker_AppResults), 
        {'Task Date': Text(Prod_DatePicker.SelectedDate, "dd/mm/yyyy")},
        {'Agent Name': User().FullName},
        {'Agent EmailAddress': User().Email},
        {'Task Type': Text("Handled")},
        {Country: Prod_DropDown_Country.Selected.Result},
        {Exception: Prod_lblException.Text},
        {Carrier: Prod_lblCarrier.Text},
        {Offered: Value(Prod_lblOffered.Text)},
        {'Calls Handled': If(IsBlank(Prod_inptCallsHandled.Text),0,(Prod_inptCallsHandled.Text))},
        {'Emails Handled': If(IsBlank(Prod_inptEmailsHandled.Text),0,(Prod_inptEmailsHandled.Text))},
        {'Handled SL1': If(IsBlank(Prod_inptSL1.Text),0,(Prod_inptSL1.Text))},
        {'Handled SL2': If(IsBlank(Prod_inptSL2.Text),0,(Prod_inptSL2.Text))},
        {'Handled SL3': If(IsBlank(Prod_inptSL3.Text),0,(Prod_inptSL3.Text))},
        {'Handled SL4': If(IsBlank(Prod_inptSL4.Text),0,(Prod_inptSL4.Text))}))

 

Again, a big thank your for your help,

Regards

Hey @Anonymous, you are getting close, but think about what we've already done - used ForAll() to iterate over multiple gallery items. So, if you have multiple nested galleries, then perhaps you need another ForAll()? 😉

 

ForAll(
    galParent.AllItems As ParentGallery,
	ForAll(
		Filter(
			AddColumns(
				ChildGallery.AllItems,
				//===Add a column for sum of Calls and Emails
				"CallsAndEmailsSum", Sum(Value(Prod_inptCallsHandled.Text), Value(Prod_inptEmailsHandled.Text)),
				//===Add a column for sum of all SL inputs
				"SLsSum", Sum(Value(Prod_inptSL1.Text), Value(Prod_inptSL2.Text), Value(Prod_inptSL3.Text), Value(Prod_inptSL4.Text))
			),
			//===Perform check: Calls + Emails is greater than zero
			//===Perform check: Calls + Emails = Sum of SL inputs
			CallsAndEmailsSum > 0 && CallsAndEmailsSum = SLsSum
		) As ChildGalleryRecord,
		Patch(PAT_Tracker_AppResults, Defaults(PAT_Tracker_AppResults), 
			{'Task Date': Text(Prod_DatePicker.SelectedDate, "dd/mm/yyyy")},
			{'Agent Name': User().FullName},
			{'Agent EmailAddress': User().Email},
			{'Task Type': Text("Handled")},
			{Country: Prod_DropDown_Country.Selected.Result},
			{Exception: Prod_lblException.Text},
			{Carrier: Prod_lblCarrier.Text},
			{Offered: Value(Prod_lblOffered.Text)},
			{'Calls Handled': If(IsBlank(Prod_inptCallsHandled.Text),0,(Prod_inptCallsHandled.Text))},
			{'Emails Handled': If(IsBlank(Prod_inptEmailsHandled.Text),0,(Prod_inptEmailsHandled.Text))},
			{'Handled SL1': If(IsBlank(Prod_inptSL1.Text),0,(Prod_inptSL1.Text))},
			{'Handled SL2': If(IsBlank(Prod_inptSL2.Text),0,(Prod_inptSL2.Text))},
			{'Handled SL3': If(IsBlank(Prod_inptSL3.Text),0,(Prod_inptSL3.Text))},
			{'Handled SL4': If(IsBlank(Prod_inptSL4.Text),0,(Prod_inptSL4.Text))}
		)
	)
)
Anonymous
Not applicable

Hi @metsshan ,

 

Thanks a lot but this one is not working. It's patching child gallery items even if the conditions in not meet.

 

Just for you knowledge,

 

here my items properties of the Parent Gallery : 

 

Distinct(Filter(PAT_Tracker_AppSettings, Country = Prod_DropDown_Country.Selected.Result),Exception)

 

 

here my items properties of the Child Gallery : 

 

Filter(PAT_Tracker_AppSettings,ThisItem.Result = Title && Country = Prod_DropDown_Country.Selected.Result)

 

 

here my OnSelect properties of the button will patch.

 

//===Filter and Patch Child Gallery items.
ForAll(
    Filter(
        AddColumns(
            ChildGallery.AllItems,
            //===Add a column for sum of Calls and Emails
            "CallsAndEmailsSum", Sum(Value(Prod_inptCallsHandled.Text), Value(Prod_inptEmailsHandled.Text)),
            //===Add a column for sum of all SL inputs
            "SLsSum", Sum(Value(Prod_inptSL1.Text), Value(Prod_inptSL2.Text), Value(Prod_inptSL3.Text), Value(Prod_inptSL4.Text))
        ),
        //===Perform check: Calls + Emails is greater than zero
        //===Perform check: Calls + Emails = Sum of SL inputs
        CallsAndEmailsSum > 0 && CallsAndEmailsSum = SLsSum
    ) As ChildGalleryRecord,
		Patch(PAT_Tracker_AppResults, Defaults(PAT_Tracker_AppResults), 
			{'Task Date': Text(Prod_DatePicker.SelectedDate, "dd/mm/yyyy")},
			{'Agent Name': ChildGalleryRecord.lblAgentName.Text},
			{'Agent EmailAddress': Text(ComboBox2.Selected.Mail)},
			{'Task Type': Text("Handled")},
			{Country: ChildGalleryRecord.Prod_lblCountry.Text},
			{Exception: ChildGalleryRecord.Prod_lblException.Text},
			{Carrier: ChildGalleryRecord.Prod_lblCarrier.Text},
			{Offered: Value(Prod_lblOffered.Text)},
			{'Calls Handled': If(IsBlank(ChildGalleryRecord.Prod_inptCallsHandled.Text),0,(ChildGalleryRecord.Prod_inptCallsHandled.Text))},
			{'Emails Handled': If(IsBlank(ChildGalleryRecord.Prod_inptEmailsHandled.Text),0,(ChildGalleryRecord.Prod_inptEmailsHandled.Text))},
			{'Handled SL1': If(IsBlank(ChildGalleryRecord.Prod_inptSL1.Text),0,(ChildGalleryRecord.Prod_inptSL1.Text))},
			{'Handled SL2': If(IsBlank(ChildGalleryRecord.Prod_inptSL2.Text),0,(ChildGalleryRecord.Prod_inptSL2.Text))},
			{'Handled SL3': If(IsBlank(ChildGalleryRecord.Prod_inptSL3.Text),0,(ChildGalleryRecord.Prod_inptSL3.Text))},
			{'Handled SL4': If(IsBlank(ChildGalleryRecord.Prod_inptSL4.Text),0,(ChildGalleryRecord.Prod_inptSL4.Text))}))

 

 

But this code is patching only the parent item selected. 

 

On the below photo, 2 items need to be patched. (numbers between () in the parent gallery return child gallery items where meet the condition).

Mts1_0-1659793833508.png

My parent gallery is used to group child item.

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