cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Update collection using UpdateIf on Choice column then Patch SharePoint List using Patch on Choice column

Hi PA community!

Happy Sunday!

 

Within my PoweApp, in OnStart property of App -> I am creating a local collection using Power Automate flow after filtering large SharePoint list 

There are a  couple of choice columns in my SharePoint list i.e. a) Early_Termination_Yes_or_No where choices are Yes / No / Unclear 

and b) Category where there are 8 choices

The PowerAutomate response schema is like below for both above columns 

powerautouser20_0-1710655211513.png

 

My collection (colSPOListItems) definition is below along with correct schema for above columns : 

powerautouser20_3-1710655509732.png

 

powerautouser20_1-1710655429851.png

 

powerautouser20_2-1710655455863.png

Gallery items are set to colSPOListItems

Gallery OnSelect property set to define a variable Set(varListItem,ThisItem)

 

The workflow of my app is that users update their changes using combo-boxes for above choice columns into the collection.

When users press submit button, these changes made in the collection get updated into the SharePoint list using Patch function.

 

I have spent hours on this problem but unable to arrive at the solution.

 

Please can someone help?

Below are the errors I encounter

 

Thanks in advance!

 

1) Combo-box OnChange property formula error

 

powerautouser20_4-1710655778844.png

powerautouser20_5-1710655829911.png

 

2) Submit Button OnSelect property formula error

The yellow highlighted part should be made dynamic but I have just hard-coded some values to demonstrate the challenge I am facing

powerautouser20_7-1710656249763.png

 

powerautouser20_6-1710656214794.png

 

3 ACCEPTED SOLUTIONS

Accepted Solutions

Hi @powerautouser20,

 

To Parse a choice column, you can use the following structure:

//Example of your ClearCollect colSPO... ForAll
{
    //Map fields to expected choice schema & define value as a text type
    EARLY_TERMINATION_YES_OR_NO: {Value: Text(Value.EARLY_TERMINATION_YES_OR_NO.Value)},
    CATEGORY: {Value: Text(Value.CATEGORY.Value)}
}

This will result in the expected SP choice column schema.

 

In order to Patch / Update this column, use the following structure:

//E.g. parameter in UpdateIf or Patch functions
{CATEGORY: {Value: "Text value here"}}

 

Please note that your UpdateIf condition may not work as expected. You may want to reference the Self.Selected property which is compared to the yes_no column:

UpdateIf(
    //Since this column is defined as a Text column above, the function is not needed
    EARLY_TERMINATION_YES_OR_NO.Value <> Self.Selected.Value,
    //Example using the new update parameter structure
    {EARLY_TERMINATION_YES_OR_NO: {Value: "No"}}
)

 

If this solves your question, would you be so kind as to accept it as a solution & give it a thumbs up.

Thanks!

View solution in original post

Hi @powerautouser20,

 

Thanks for the additional information. Is category a LookUp column instead of a choice column by any chance?

 

To solve the error, let's add Id to our JSON parsing and patch parameter:

 

//ParseJSON
CATEGORY: {Value: Text(Value.CATEGORY.Value), Id: Value(Value.CATEGORY.Id)}

//Patch (expects Choices(ListName.CATEGORY) to be your Items property)
//(Or a table with the Value & Id column schema)
{CATEGORY: ComboBox1.Selected}

 

Should the combobox not contain the Choices() function as items property, you will have to provide the record schema manually within the Patch function:

 

//Primary column is the main column selected within the 'Select a column' dropdown (see column settings in SP)
{CATEGORY: {Value: ComboBox1.Selected.PrimaryColumn, Id: ComboBox1.Selected.ID}}

 

I hope this helps!

View solution in original post

I think I figured it out.

The problem with my Patch formula is that PowerApps doesn't know which item within SPO List to update with the update record.

So I establish that missing information (underlined above) using LookUp.

I had almost got it in my previous post

 

The updated Patch formula is : 

 

Patch(List_FinalTracker3,
    LookUp(List_FinalTracker3,UNIQUE_ID=Text(Gallery2.Selected.UNIQUE_ID)),  
   
        {CATEGORY:{Value:ComboBox1.Selected.Value, Id:ComboBox1.Selected.Id},
        EARLY_TERMINATION_YES_OR_NO: {Value:ComboBox2.Selected.Value},
        COMMENTS:TextInput1_3.Text,
        IF_NOT_TERMINATED_NEW_ACCT_NO:TextInput1_1.Text
        }
       
   
)
 
Thanks @LaurensM for all your support !

View solution in original post

11 REPLIES 11

hey @powerautouser20 

 

please copy paste your code here so we do not need to retype,

 

thanks in advance

Hi @powerautouser20,

 

To Parse a choice column, you can use the following structure:

//Example of your ClearCollect colSPO... ForAll
{
    //Map fields to expected choice schema & define value as a text type
    EARLY_TERMINATION_YES_OR_NO: {Value: Text(Value.EARLY_TERMINATION_YES_OR_NO.Value)},
    CATEGORY: {Value: Text(Value.CATEGORY.Value)}
}

This will result in the expected SP choice column schema.

 

In order to Patch / Update this column, use the following structure:

//E.g. parameter in UpdateIf or Patch functions
{CATEGORY: {Value: "Text value here"}}

 

Please note that your UpdateIf condition may not work as expected. You may want to reference the Self.Selected property which is compared to the yes_no column:

UpdateIf(
    //Since this column is defined as a Text column above, the function is not needed
    EARLY_TERMINATION_YES_OR_NO.Value <> Self.Selected.Value,
    //Example using the new update parameter structure
    {EARLY_TERMINATION_YES_OR_NO: {Value: "No"}}
)

 

If this solves your question, would you be so kind as to accept it as a solution & give it a thumbs up.

Thanks!

@LaurensM ,

Thanks for the detailed reply.

I updated my collection definition as suggested by you

 
EARLY_TERMINATION_YES_OR_NO: {Value: Text(Value.EARLY_TERMINATION_YES_OR_NO.Value)},
CATEGORY: {Value: Text(Value.CATEGORY.Value)}
 
I updated the OnChange property of the combo-box buttons as suggested by you, sample below:
 
UpdateIf(colSPOListItems,
    EARLY_TERMINATION_YES_OR_NO.Value <> Self.Selected.Value,
    {EARLY_TERMINATION_YES_OR_NO:{Value:Self.Selected.Value}})
 
So far, so good!
 
I still get an error in the Patch formula which is bound to "SUBMIT" button OnSelect property, see code below
I used the structure described by you 
 
Patch(List_FinalTracker3,
{CATEGORY: {Value:ComboBox1.Selected.Value}}
)
 
powerautouser20_1-1710682353447.png

 


Any ideas about this?

Is the error occurring due to the way CATEGORY is represented in SharePoint list ??

 

This is definitely much progress than today morning, appreciate your help !

hi @mmbr1606 ,

I will note for future, thanks for the headsup

 

 

Hi @powerautouser20,

 

Thanks for the additional information. Is category a LookUp column instead of a choice column by any chance?

 

To solve the error, let's add Id to our JSON parsing and patch parameter:

 

//ParseJSON
CATEGORY: {Value: Text(Value.CATEGORY.Value), Id: Value(Value.CATEGORY.Id)}

//Patch (expects Choices(ListName.CATEGORY) to be your Items property)
//(Or a table with the Value & Id column schema)
{CATEGORY: ComboBox1.Selected}

 

Should the combobox not contain the Choices() function as items property, you will have to provide the record schema manually within the Patch function:

 

//Primary column is the main column selected within the 'Select a column' dropdown (see column settings in SP)
{CATEGORY: {Value: ComboBox1.Selected.PrimaryColumn, Id: ComboBox1.Selected.ID}}

 

I hope this helps!

My bad ... Category is indeed a LookUp column, let me try your latest suggestion!

@LaurensM ,

The ComboBox1 Items property is set at Choices(ListName.CATEGORY)

Similarly, the ComboBox2 Items property is set at Choices(ListName.EARLY_TERMINATION_YES_OR_NO)

 

The OnChange properties for the Combo-boxes are below:

 

ComboBox1: 

UpdateIf(colSPOListItems,
    CATEGORY.Value <> Self.Selected.Value,
    {CATEGORY: ComboBox1.Selected})

 

ComboBox2 : 

UpdateIf(colSPOListItems,
    EARLY_TERMINATION_YES_OR_NO.Value <> Self.Selected.Value,
    {EARLY_TERMINATION_YES_OR_NO:{Value:Self.Selected.Value}})
 
 

I am using below in my Patch formula, as suggested by you

{CATEGORY: ComboBox1.Selected}

 

All the 'compile' errors have disappeared ! 

 

Now I am getting a run-time error, please see below screenshot

powerautouser20_0-1710686046892.png

 

The 'OnSelect' property of my Submit button has the below code: 

 

Patch(List_FinalTracker3,
{CATEGORY: ComboBox1.Selected},
{EARLY_TERMINATION_YES_OR_NO: {Value:ComboBox2.Selected.Value}}
)

 

If I try your alternate suggestion within Patch formula i.e. 

{CATEGORY: {Value: ComboBox1.Selected.PrimaryColumn, Id: ComboBox1.Selected.ID}}

then I get below error

powerautouser20_1-1710686432393.png

Any suggestion to get rid of the runtime error?

 

Thanks in advance!

 

 

 

@powerautouser20,

 

Does the error remain when using the following Patch structure:

Patch(
    List_FinalTracker3,
    //New record creation patch
    Defaults(List_FinalTracker3),
    //Mention both columns within the same update parameter
    {
        CATEGORY: ComboBox1.Selected,
        EARLY_TERMINATION_YES_OR_NO: ComboBox2.Selected
    }
)

 

I hope this helps!

Hi @LaurensM ,

Thank you - the run-time error is gone.

 

However, there is no update to the Data Source (List_FinalTracker3)

There is no new record / existing record is not updated

 

The collection gets updated

To verify this, I created two text labels referencing the collection values for CATEGORY, EARLY_TERMINATION_YES_OR_NO

 

Formulae used 

Label_CATEGORY --> "CATEGORY_Value_from_collection: " &  LookUp(colSPOListItems,UNIQUE_ID=Text(17xxxxx6),CATEGORY.Value)
 
Label_EARLY_TERMINATION --> 
"EARLY_TERMINATION_YES_OR_NO_Value_from_collection: " & LookUp(colSPOListItems,UNIQUE_ID=Text(17xxxxx6),EARLY_TERMINATION_YES_OR_NO.Value)

 

Below is a 'BEFORE' screenshot i.e. when I refresh the App by pressing App -> Run OnStart

 

powerautouser20_4-1710722070105.png

 

The collection values match those with my list (filtered for UNIQUE_ID: 17xxxxx6)

powerautouser20_1-1710721636751.png

AFTER screenshot(s) upon clicking SUBMIT button

 

 

AFTER SharePoint list screenshot (filtered for UNIQUE_ID: 17xxxxx6)

powerautouser20_3-1710721878514.png

Moreover, in my process, new records should not be created i.e. only existing records to be updated

 

 

I think we are getting there - one step at a time!

 

Thanks for your support

 

Please tell me if you know what's happening with the Patch function, reproduced below (latest one I am using)

 

Patch(
    List_FinalTracker3,
    //New record creation patch
    Defaults(List_FinalTracker3),
    //Mention both columns within the same update parameter
    {
        CATEGORY: ComboBox1.Selected,
        EARLY_TERMINATION_YES_OR_NO: ComboBox2.Selected
       
    }
)

 

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