cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
DCHammer
Responsive Resident
Responsive Resident

Patching the 'parent' table from a gallery

So the section of code that is about to follow is on the OnSelect of an Icon in a gallery. 

The first section patches a record in a list if varGalEdit is true. That same variable helps control visibility of a bunch of things based on current user etc.

This works correctly as does the reset of varGalEdit immediately below.

The next IF statement is trying to determine if 'SPIFF - Approvals' has records that match the number of approvers with the same approve_level. It would honestly be better if that IF statement didn't just compare counts but actually verified that there was a specific record in 'SPIFF - Approvals' for each 'SPIFF - Approvers'.Approver where the Approve_Level matched the Approve_Level from galItems but for now I'm satisfied using CountRows since the UI and input controls ensures the right results even though it's really not right.

I have a problem there I can't figure out to start with. Approver.Email = Approver is wrong. This specific statement:

Filter(
   'SPIFF - Approvals',
   Approver.Email = Approver
       && PositionID = galItems.Selected.ID
       )

I think the UpdateContext statements are correct but until I can get the upper part working, they aren't even processing.

Then after all of this happens, I want to Patch the 'SPIFF - Requests' record which is galItems.Selected and set the Approve_Level based on the results from the CountRows comparison.

If(
    varGalEdit = true,
    Patch(
        'SPIFF - Approvals', // The target data source
        LookUp(
            'SPIFF - Approvals',
            ID = galApprovals.Selected.ID
        ), // Identify the specific record
        {
            Comments: txtApproverComment.Text,
            // Update or set the value of Comments column
            // Add more columns and values as needed
            Status: rdoApproveEdit.Selected
            // Update or set the value of Status column
            // Add more columns and values as needed
        }
    ),
    Set(
        varGalEdit,
        false
    ),
    If(
        CountRows(
            Filter(
                'SPIFF - Approvers',
                Approve_Level = galApprovals.Selected.Approval_Level
            )
        ) = CountRows(
            Filter(
                'SPIFF - Approvers',
                Approve_Level = galApprovals.Selected.Approval_Level &&
                !IsEmpty(
                    Filter(
                        'SPIFF - Approvals',
                        Approver.Email = Approver
                            && PositionID = galItems.Selected.ID
                    )
                )
            )
        ),
        UpdateContext(
            {
                varNewApprovalLevel: galItems.Selected.Approval_Level + 1
            }
        ),
        UpdateContext(
            {
                varNewApprovalLevel: galItems.Selected.Approval_Level
            }
        )
    ),
    Patch(
        galItems, // The target data source (e.g., SharePoint list)
        galItems.Selected, // Identify the specific record
        {
            Approve_Level: varNewApprovalLevel
            // Update or set the value of Approval_Level column
            // Add more columns and values as needed
        }
    )
)

 

Thanks in advance to whomever takes the time to read this.

 

1 ACCEPTED SOLUTION

Accepted Solutions
DCHammer
Responsive Resident
Responsive Resident

Here is what I finally came up with. I'm sure there are far cleaner ways to make this work but it does so I'm leaving it alone.

I didn't originally have that last Patch statement inside an If. Since the context variable was being set appropriately above, patching the record always resulted in the same value but in a bunch of cases would create unnecessary updates. So I changed it. 

If I was really concerned about data integrity, I should modify the CountRows section to actually determine if the Users with an Approve_Level that matches the varItem have their own individual records in the Approval list but I have enough control around who can create approval records that using CountRows is going to always work.

 

If(
    varGalEdit = true,
    Patch(
        'SPIFF - Approvals',// The target data source (e.g., SharePoint list)
        LookUp(
            'SPIFF - Approvals',
            ID = galApprovals.Selected.ID
        ),// Identify the specific record
        {
            Comments: txtApproverComment.Text,
            // Update or set the value of Comments column
            // Add more columns and values as needed
Status: rdoApproveEdit.Selected
            // Update or set the value of Status column
// Add more columns and values as needed
        }
    ),
    Set(
        varGalEdit,
        false
    )
);
If(
    CountRows(
        Filter(
            'SPIFF - Approvers',
            Approve_Level = varItem.Approval_Level
        )
    ) = CountRows(
        Filter(
            'SPIFF - Approvals',
            Approve_Level = varItem.Approval_Level && PositionID = varItem.ID
        )
    ),
    UpdateContext({varNewApprovalLevel: varItem.Approval_Level + 1}),
    UpdateContext({varNewApprovalLevel: varItem.Approval_Level + 0})
);
If(
    varNewApprovalLevel <> varItem.Approval_Level,
    Patch(
        'SPIFF - Requests',// The target data source (e.g., SharePoint list)
        LookUp(
            'SPIFF - Requests',
            ID = varItem.ID
        ),// Identify the specific record
        {Approval_Level: varNewApprovalLevel
        // Update or set the value of Approval_Level column
// Add more columns and values as needed
}
    );
    UpdateContext ({varNewApprovalLevel: Blank()})
);
If(
    varGalEdit = false,
    Set(
        varGalEdit,
        true
    ),
    Set(
        varGalEdit,
        false
    )
)

 

Kinda proud of figuring this one out on my own. Thanks for attending.

View solution in original post

3 REPLIES 3
DCHammer
Responsive Resident
Responsive Resident

Forget reading the OP. I made some changes that have been at least partially successful.

 

Everything now gets past the interpreter. It no longer thinks there are errors in this and it will proc. But it's not completing the final Patch and updating the record. 

 

I think I have a problem with my nested IFs but I can't figure it out. My assumption is that the If statement is evaluating such that it's not even processing the final Patch statement. I know it works up to and including the UpdateContext statements. Because I manually create the data conditions for the CountRows comparison to succeed and/or fail, the context variable is setting correctly. But regardless of that outcome, the final Patch doesn't execute.

 

If(
    varGalEdit = true,
    Patch(
        'SPIFF - Approvals',// The target data source (e.g., SharePoint list)
        LookUp(
            'SPIFF - Approvals',
            ID = galApprovals.Selected.ID
        ),// Identify the specific record
        {
            Comments: txtApproverComment.Text,
            // Update or set the value of Comments column
            // Add more columns and values as needed
Status: rdoApproveEdit.Selected
            // Update or set the value of Status column
// Add more columns and values as needed
        }
    ),
    Set(
        varGalEdit,
        false
    ),
    If(
        CountRows(
            Filter(
                'SPIFF - Approvers',
                Approve_Level = varItem.Approval_Level
            )
        ) = CountRows(
            Filter(
                'SPIFF - Approvals',
                Approve_Level = varItem.Approval_Level && PositionID = varItem.ID
            )
        ),
        UpdateContext({varNewApprovalLevel: varItem.Approval_Level + 1}),
        UpdateContext({varNewApprovalLevel: varItem.Approval_Level + 0})
    ),
    Patch(
    'SPIFF - Requests', // The target data source (e.g., SharePoint list)
    LookUp(
        'SPIFF - Requests',
        ID = varItem.ID
    ), // Identify the specific record
    {
        Approval_Level: varNewApprovalLevel
        // Update or set the value of Approval_Level column
        // Add more columns and values as needed
    }
)

);
DCHammer
Responsive Resident
Responsive Resident

So it occurred to me on my drive home that I need to separate the first IF statement from the second. This isn't a single transaction. The first If processes regardless of the outcome of the second. So I'll 'commit' the change to the gallery item with the first If and close that loop and reset the varGalEdit variable.

Then process the second If to determine if the records are such that the value on the varItem needs to be patched.

I also realize as I'm typing this that it was always going to fail the way it's currently structured even if the nested Ifs were correct.

Since this same code is what actually creates or updates the approval records that are then later analyzed for existence, it was going to fail when the last person in the flow created their approval.

I'll update this later today with what I manage to make work.

DCHammer
Responsive Resident
Responsive Resident

Here is what I finally came up with. I'm sure there are far cleaner ways to make this work but it does so I'm leaving it alone.

I didn't originally have that last Patch statement inside an If. Since the context variable was being set appropriately above, patching the record always resulted in the same value but in a bunch of cases would create unnecessary updates. So I changed it. 

If I was really concerned about data integrity, I should modify the CountRows section to actually determine if the Users with an Approve_Level that matches the varItem have their own individual records in the Approval list but I have enough control around who can create approval records that using CountRows is going to always work.

 

If(
    varGalEdit = true,
    Patch(
        'SPIFF - Approvals',// The target data source (e.g., SharePoint list)
        LookUp(
            'SPIFF - Approvals',
            ID = galApprovals.Selected.ID
        ),// Identify the specific record
        {
            Comments: txtApproverComment.Text,
            // Update or set the value of Comments column
            // Add more columns and values as needed
Status: rdoApproveEdit.Selected
            // Update or set the value of Status column
// Add more columns and values as needed
        }
    ),
    Set(
        varGalEdit,
        false
    )
);
If(
    CountRows(
        Filter(
            'SPIFF - Approvers',
            Approve_Level = varItem.Approval_Level
        )
    ) = CountRows(
        Filter(
            'SPIFF - Approvals',
            Approve_Level = varItem.Approval_Level && PositionID = varItem.ID
        )
    ),
    UpdateContext({varNewApprovalLevel: varItem.Approval_Level + 1}),
    UpdateContext({varNewApprovalLevel: varItem.Approval_Level + 0})
);
If(
    varNewApprovalLevel <> varItem.Approval_Level,
    Patch(
        'SPIFF - Requests',// The target data source (e.g., SharePoint list)
        LookUp(
            'SPIFF - Requests',
            ID = varItem.ID
        ),// Identify the specific record
        {Approval_Level: varNewApprovalLevel
        // Update or set the value of Approval_Level column
// Add more columns and values as needed
}
    );
    UpdateContext ({varNewApprovalLevel: Blank()})
);
If(
    varGalEdit = false,
    Set(
        varGalEdit,
        true
    ),
    Set(
        varGalEdit,
        false
    )
)

 

Kinda proud of figuring this one out on my own. Thanks for attending.

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