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
LaurensM
Super User
Super User

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
mmbr1606
Super User
Super User

hey @powerautouser20 

 

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

 

thanks in advance

LaurensM
Super User
Super User

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

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 (1,693)