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

Update and Create SP List Items using Patch from multi-screen form

Hey guys, I have an issue I'm trying to work through but I cant seem to solve it. I have a SharePoint List that is broken into 6 separate screens based on sections, I.e. Section A, B, C.... When the form is created from the 'New' Button, all the subsequent forms are set to FormMode.New, and when the user is editing a previous entry, the forms are all FormMode.Edit so that I can utilize the 'Item' Property. On the last page of the form, I need to submit everything, So I check what mode the form is in, and then patch the form to my SP List as follows:

 

If(IsFormInvalid = false,
	If(IRFormSectionG_Form.Mode = FormMode.New,
		Patch(
			Collection, 
			Defaults(Collection),
			IRFormSectionA_Form.Updates,
			IRFormSectionB_Form.Updates,
			IRFormSectionC_Form.Updates,
			IRFormSectionD_Form.Updates,
			IRFormSectionEF_Form.Updates,
			IRFormSectionG_Form.Updates
		),
		Patch( 
			Collection,
                        QueryFilter,
	                IRFormSectionA_Form.Updates,
			IRFormSectionB_Form.Updates,
			IRFormSectionC_Form.Updates,
			IRFormSectionD_Form.Updates,
			IRFormSectionEF_Form.Updates,
			IRFormSectionG_Form.Updates 
		)
	)
);

I've verified that the QueryFilter, I.e. the item from the SP list that I want to update is the correct one, but for whatever reason, when the form is in edit mode and I submit, nothing happens. No new records are added or updated but according to the documentation, this should be correct. Any thoughts?

1 ACCEPTED SOLUTION

Accepted Solutions

My suggestion is that when working with SharePoint, place a Refresh() action ahead of operations.

So ahead of selecting an item to edit, insert a Refresh:

 

// Refresh the datasource.
Refresh(datasource_name);

// Set the selected item to a variable to be referenced in forms.
Set(displayItem,ThisItem);

// Go to the next screen.
Navigate(IRFormSectionA,ScreenTransition.None)

 

 

You can hold the selected item temporarily using With() and use Lookup to very explicitly get the record from SharePoint:

 

With(
    {
        selectedRecord: ThisItem
    },
    Refresh(datasource_name);
    Set(displayItem,LookUp(datasource_name,ID=selectedRecord.ID));
    Navigate(IRFormSectionA,ScreenTransition.None)
)

 


It looks like displayItem is used on all the screens so it is best to set it to a global variable instead of local. This is done by using Set() as in the examples above.

View solution in original post

7 REPLIES 7

Hi @OwninJoe ,

Can you share the formula you use for setting the form mode? Do you perform a Refresh() on the SharePoint list at any point?

I set the form mode when the user selects either "New" or "Edit" with the following:

 

NewForm(IRFormSectionA_Form);
NewForm(IRFormSectionB_Form);
NewForm(IRFormSectionC_Form);
NewForm(IRFormSectionD_Form);
NewForm(IRFormSectionEF_Form);
NewForm(IRFormSectionG_Form);

Navigate(IRFormSectionA, Transition.Push);

 

From there, every time the user continues through the form by selecting "Next", I simply use Navigate(IRFormSection-); since the form mode should already be set to either 'New' or 'Edit. Finally, On the 'submit' action, I check the form mode based on the last section and patch accordingly.

Can you share the formula you use for setting the form mode to edit mode and when/where this occurs? Is QueryFilter a variable? 

From a gallery, I've added the following code to the onSelect of the item to allow for editing:

EditForm(IRFormSectionA_Form);
EditForm(IRFormSectionB_Form);
EditForm(IRFormSectionC_Form);
EditForm(IRFormSectionD_Form);
EditForm(IRFormSectionEF_Form);
EditForm(IRFormSectionG_Form);
Navigate(IRFormSectionA,ScreenTransition.None, {displayItem:ThisItem})

This switches all forms to edit mode and then passes the currently selected item to the first form on navigation to be used as the Item property of the form.

 

When a user creates a new form, the select the new button and the following code is associated with that buttons onSelect method:

NewForm(IRFormSectionA_Form);
NewForm(IRFormSectionB_Form);
NewForm(IRFormSectionC_Form);
NewForm(IRFormSectionD_Form);
NewForm(IRFormSectionEF_Form);
NewForm(IRFormSectionG_Form);
Navigate(IRFormSectionA, Transition.Push);

 In this scenario, there is no selected item to pass with the navigation change, and all forms are set to the new EditForm mode.

 

Once the user completes section A, and all subsequent sections, the 'Next' button onSelect looks like this:

If(IsFormInvalid = false,
Navigate(IRFormSectionB, Transition.None, {displayItem:displayItem})
);

So once the user finishes section A and clicks 'next', we check if the form is valid, and then we navigate to the next section of the form passing along the displayItem. This display item is only valid when the form is in edit mode and should be ignored otherwise.

 

QueryFilter is a variable that I set to get the current item's associated sharepoint list item in order to update it using patch(). Currently, if the form is in the 'New' mode, the QueryFilter is skipped and we use default(SPList) in it's place as per the MS documentation.

My suggestion is that when working with SharePoint, place a Refresh() action ahead of operations.

So ahead of selecting an item to edit, insert a Refresh:

 

// Refresh the datasource.
Refresh(datasource_name);

// Set the selected item to a variable to be referenced in forms.
Set(displayItem,ThisItem);

// Go to the next screen.
Navigate(IRFormSectionA,ScreenTransition.None)

 

 

You can hold the selected item temporarily using With() and use Lookup to very explicitly get the record from SharePoint:

 

With(
    {
        selectedRecord: ThisItem
    },
    Refresh(datasource_name);
    Set(displayItem,LookUp(datasource_name,ID=selectedRecord.ID));
    Navigate(IRFormSectionA,ScreenTransition.None)
)

 


It looks like displayItem is used on all the screens so it is best to set it to a global variable instead of local. This is done by using Set() as in the examples above.

v-xida-msft
Community Support
Community Support

Hi @OwninJoe ,

How do you set up your QueryFilter variable? Could you please share more details about the formula?

 

Based on the formula that you mentioned, I could not find any syntax error with it. Please make sure the QueryFilter variable stores a record value which you want to update from your SP List.

 

I found that you have typed Collection as data source in your Patch formula, is it your SP List, or it is just a Collection variable. I have made a test on my side, please try to modify your formula as below:

If(
   IsFormInvalid = false,
   Patch(
         'Your SP List',  // replace it with your own actual SP List name
	   If(
              IRFormSectionG_Form.Mode = FormMode.New,
              Defaults('Your SP List'),
              LookUp('Your SP List', ID = QueryFilter.ID)  // I assume that the QueryFilter variable stores the SP List Item record you want to update
           ),
	   IRFormSectionA_Form.Updates,
	   IRFormSectionB_Form.Updates,
           IRFormSectionC_Form.Updates,
	   IRFormSectionD_Form.Updates,
	   IRFormSectionEF_Form.Updates,
	   IRFormSectionG_Form.Updates
  )
);

Please try above formula, check if the issue is solved.

 

If above formula still could not work, I think this issue may be related to the QueryFilter variable that you mentioned. Please consider add the following formula within the OnSelect property of the Gallery:

Set(QueryFilter, ThisItem);  // Add this formula
EditForm(IRFormSectionA_Form);
EditForm(IRFormSectionB_Form);
EditForm(IRFormSectionC_Form);
EditForm(IRFormSectionD_Form);
EditForm(IRFormSectionEF_Form);
EditForm(IRFormSectionG_Form);
Navigate(IRFormSectionA,ScreenTransition.None, {displayItem:ThisItem})

 

Best regards,

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Thanks for the help! looks like this worked. I think my issue was although I thought that the query item referred to the correct item, it didn't. So what I did was follow your steps and do a lookup to my SP list based on the selected item, ThisItem, and then used that as a global variable rather than passing the variable between each screen. I also then updated the patch method to remove the QueryFilter variable that I had and replaced it with the ThisItem variable that I had set because that's the item that needs to be updated.

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

Top Solution Authors
Top Kudoed Authors
Users online (2,176)