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

Patch : Multiple screens to one record SharePoint - update brings error in fx.

Hi,

 

I am getting this error message:

Patch(source,record,update,....)

update:The update that needs to be patched to the given record

 

emphasis on the update.

 

 

I have:

Patch(GeneralHSEAudit_Mobile,MyRecord,{Title:EditScreen1.Title.text,ConductedOn:EditScreen1.ConductedOn.Value,PreparedBy:EditScreen1.PreparedBy.Text,PreferredName:EditScreen1.PreferredName.Text:Location:EditScreen1.Text,Personnel:EditScreen1.Text,’1.1_Reviewed’:EditScreen1.’1.1_Reviewed’.Value,’1.2_Outstanding’:EditScreen1.’1.2_Oustanding’.value,‘1.3_AllSite’:EditScreen1.’1.3_AllSite’.value,‘1.4_Comments’:EditScreen1.’1.4_Comments’.text,’2.1_Plan’:EditScreen1.’2.1_Plan’.value,’2.2_Trial’:EditScreen1.’2.2_Trial’.value,..................’16.7_OtherSeats’:EditScreen6.’16.7_OtherSeats’.value,’16.8_WindScreen’:EditScreen6.’16.8_WindScreen’.value,’16.9_Vehicles’:EditScreen6.’16.9_Vehicles’.value,’16.10_Storage’:EditScreen6.’16.10_Storage’.value,’16.11_Comments’:EditScreen6.’16.11_Comments’.text})

 

Is not the update between the { } ?

 

Dang this is a TAD not clear.

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

Okay, so it looks like my assumption of the problem statement is correct. Let's start with that!

 

My advice is to jump back when you run into a head scratcher. You might find a better way.

 

So, I will offer a quick - here's a better way:  

1) I don't know what your starting point is.  Typically these things come from some Gallery or other "selected" item.  So, I'm going to assume a Gallery (Gallery1).  I know you mention you have a MyRecord you set, but you might not even need that if you are coming off of a Gallery.  If this is not the case, then substitute the "selected" items below with your MyRecord.

 

2) Since you are working with EditForm Controls, what you can simply do is this - 

For each of the 6 forms, set the dataSource to the proper dataSource (you most likely have this already - GeneralHSEAudit_Mobile)

Set the Item property to Gallery1.Selected

 

3) On the Check mark Icon you have on the final screen, add this to the OnSelect action:

   SubmitForm(EditForm1); SubmitForm(EditForm2); SubmitForm(EditForm3); SubmitForm(EditForm4); SubmitForm(EditForm5); SubmitForm(EditForm6)

 

Done!

 

If you still want to take the Patch path, then Patch(GeneralHSEAudit_Mobile, MyRecord, EditForm1.Updates, EditForm2.Updates, EditForm3.Updates, EditForm4.Updates, EditForm5.Updates, EditForm6.Updates)

 

 

See if any of this makes sense and works for you.

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

View solution in original post

13 REPLIES 13
Anonymous
Not applicable

Update - I removed the { } and still get the same result.

What I have are 6 screens in edit mode for one record to update / Patch.

Why six screens? - 160  radio buttons need  that many screens to resolve/render - otherwise the download for one screen that shows them all is a no go.

 

It is the last screen - EditScreen6 that contains the update button.

 

What am I doing wrong????

v-xida-msft
Community Support
Community Support

Hi @Anonymous,

Could you please share more details about the error message with your formula?

Do you add each Edit form control within your 6 Edit screens?

Are these ConductedOnPreparedBy, ... all controls within your EditScreen1?

If the ConductedOnPreparedBy, ... all controls within your EditScreen1, and the EditScreen1, EditScreen2, ...EditScreen6 are all Edit Screens in your app, based on the formula that you mentioned, I think there is something wrong with it.

Please take a try to modify your formula as below:

Patch(
GeneralHSEAudit_Mobile,
MyRecord,
{
Title: Title.Text, /* <-- Please replace EditScreen1.Title.Text with Title.Text, in other words, remove all 'EditScreen1', 'EditScreen2', ..., 'EditScreen6' prefix */
ConductedOn: ConductedOn.Value,
PreparedBy: PreparedBy.Text,
PreferredName: PreferredName.Text,
...
'2.2_Trial': '2.2_Trial'.value,
...
'16.7_OtherSeats': '16.7_OtherSeats'.value,
'16.8_WindScreen': '16.8_WindScreen'.value,
'16.9_Vehicles': '16.9_Vehicles'.value,
...
}
)

In addition, please also make sure the TitleConductedOnPreparedBy, PreferredName, ... etc properties you specified within the '{ }' are all existed within the Record (MyRecord) you want to update. Also please check if you have provided valid values for the corresponding properties within the '{ }' body.

The standard Patch formula to update one record within a data source as below:

Patch(
         'YourDataSource',
          RecordYouWantToUpdate,  /* <-- Find the record you want to update using LookUp function or Filter and First function*/
          {
            Column1: "xxxx",
            Column2: "xxxx",
            Column3: "xxxx",
            ....
          }
)

More details about the Patch function, please check the following article:

Patch function

 

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.
Anonymous
Not applicable

Thanks,

 

Do you add each Edit form control within your 6 Edit screens? - Yes I do

Are these ConductedOnPreparedBy, ... all controls within your EditScreen1? - yes these are on EditScreen1.

EditScreen1 contains conducted on thru to 5.6

EditScreen2 from 6.1 thru to 8.5

EditScreen3 from 9.1 thru to 10.13

EditScreen4 from 11.1 thru 12.22

EditScreen5 from 13.1 thru 14.13

EditScreen6 from 15.1 thru to 16.11 

 

I wish to patch all these screens in one update in case someone changes a question / radiobutton or adds a comment to the audit after some time.

 

Thanks

 

Hi @Anonymous,

Do these Edit form controls within your 6 Edit screen connect to same data source?

If these Edit form controls within your 6 Edit screen connect to same data source, I think you could consider take a try to modify your formula as below:

Patch(
         'YourDataSource',
          RecordYouWantToUpdate,  /* <-- Find the record you want to update using LookUp function or Filter and First function*/
          EditForm1.Updates,
EditForm2.Updates,
...
EditForm6.Updates )

Please take a try to check if you have provided valid/proper value for corresponding column within the '{ }' part in your Patch formula.

In addition, please also check if the column name you specified within the '{ }' part in your Patch formula is already existed within the Record (MyReocrd you mentioned) you want to update.

Please check and see if my response within the following thread would help in your scenario:

https://powerusers.microsoft.com/t5/Creating-Apps/Save-2-forms-from-2-pages/m-p/206525

 

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.
Anonymous
Not applicable

Thank you.

All six  edit screens are attached to the same data source - a SharePoint list.

From the Browse screen a record is selected - unique ID - from the Detail screen of that record - the user selects edit and the first editscreen opens, and progressive screens as the user steps forward. On the last EditScreen6 is the update/upload changes button.

Hense all the edit screens are tied to that record which is on a SharePoint list.

Using Myrecord to stipulate the current record which is being editted, and figure that now (thank you to your help) all the editscreens are tied to that current unique record.

I am unsure, how to be honest, the lookup will work?

 

I have checked and rechecked all column names and spellings (but murphy will dicatate that syntax somewhere is a wee bit wrong) between the { }.

 

Anonymous
Not applicable

Hello, I have modified my "fx" (in onselect) to remove all mention of EditScreen1 thru EditScreen6 and still get same error per attached - still no joy.

Dang what am I doing wrong?

@AnonymousI believe that @v-xida-msft was taking you in a good direction.

Why are you listing each and every field in your patch statement??

 

If I read your problem properly...

You have 6 screens. 

Each screen contains an Edit form. 

Each Edit form is connected to the same data source.

Each Item of the form is connected to a single record. (myRecord)

You want to actually perform the Patch/Update after the final entry screen is completed.

 

If this is the case, then consider using the Updates property of the Edit Form.  It will have any and all changes that were made on the form.

If you do the patch that was give by @v-xida-msft.  You will get a complete update from all of the edit forms into one record.

Patch(
         'YourDataSource',
          MyRecord,  RecordYouWantToUpdate,  /* <-- Find the record you want to update using LookUp function or Filter and First function*/
          EditForm1.Updates,
          EditForm2.Updates,
          ...
          EditForm6.Updates
)

You don't need to go through the pain of trying to patch and name each and every element/field of your edit forms to the patch statement.  The Updates property will hold all of that information for you.  You just do a patch and include it all and they will all be put together in your record.

 

See if that is helpful.

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!
Anonymous
Not applicable

Hi, Thank you for your valued response.

 

Why are you listing each and every field in your patch statement?? - because I do not know what I dont know, and am pretty ignorant of Patch as no real life examples to follow. Just trying to adapt all valued suggestions together.

 

 I read your problem properly...

You have 6 screens. - yes to be able to edit any changes to any or all radio buttons 

Each screen contains an Edit form.  - Yes to be able to change requires one record of 160 columns spread over 6 screens

Each Edit form is connected to the same data source. - Yes correct

Each Item of the form is connected to a single record. (myRecord) - yes that unique record of 160 columns chosen to be editted - the current record with its 160 columns and unique ID.

You want to actually perform the Patch/Update after the final entry screen is completed. - yes as cannot get the whole record to show on one screen - when first saved, the complete record of 160 radio buttons is able to be shown on one screen - just scrowls allot to the end.

 

If this is the case, then consider using the Updates property of the Edit Form.  It will have any and all changes that were made on the form. - ????????????????????????????????????????

If you do the patch that was give by @v-xida-msft.  You will get a complete update from all of the edit forms into one record - mmmmmmmmmmmmm yes - that is the hope to capture any or all possible changes which have been made to any or all radio buttons or say comments added after the fact.

 

Yup I dont know what I dont know or what to ask. Basically trying to recreate a working InfoPath form in PowerApps.

Where I can open a record make heaps of changes on the one form and then re upload with corections - only I have to use 6 screens .

Okay, so it looks like my assumption of the problem statement is correct. Let's start with that!

 

My advice is to jump back when you run into a head scratcher. You might find a better way.

 

So, I will offer a quick - here's a better way:  

1) I don't know what your starting point is.  Typically these things come from some Gallery or other "selected" item.  So, I'm going to assume a Gallery (Gallery1).  I know you mention you have a MyRecord you set, but you might not even need that if you are coming off of a Gallery.  If this is not the case, then substitute the "selected" items below with your MyRecord.

 

2) Since you are working with EditForm Controls, what you can simply do is this - 

For each of the 6 forms, set the dataSource to the proper dataSource (you most likely have this already - GeneralHSEAudit_Mobile)

Set the Item property to Gallery1.Selected

 

3) On the Check mark Icon you have on the final screen, add this to the OnSelect action:

   SubmitForm(EditForm1); SubmitForm(EditForm2); SubmitForm(EditForm3); SubmitForm(EditForm4); SubmitForm(EditForm5); SubmitForm(EditForm6)

 

Done!

 

If you still want to take the Patch path, then Patch(GeneralHSEAudit_Mobile, MyRecord, EditForm1.Updates, EditForm2.Updates, EditForm3.Updates, EditForm4.Updates, EditForm5.Updates, EditForm6.Updates)

 

 

See if any of this makes sense and works for you.

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

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 (680)