Using Customized Form with multiple screens. Patching creates new item instead of updating current

[jcollins]

I am using the a customized form with 2 screens to collect some data. When the users click Save, i want the data on both screen to create 1 record with all the data from both screens.  I learned that just by clicking Save only saved the data on the last screen only,  so I needed to also Patch the data on the 1st screen to the same record. 

This is my onSave: 

Patch('Credit Card Auth Form',Defaults('Credit Card Auth Form'), SharePointForm1.Updates, SharePointFormPay.Updates,);ResetForm(SharePointForm1);ResetForm(SharePointFormPay);RequestHide()

This works when a user creates a New form. All data gets submitted to a record. 

But now, if that record needs to be modifed, what it does is simply creates a New record with JUST the changed field instead of modifying the existing record.   

My questions are: 

1. do i need to do a patch for both screen or just the first one? 

2. How can i prevent the issue of a new record being created when i just want to edit the one i'm in? 

3. Is everthing just harder when using a customize form? Should i just create an app from scratch so it has separate view/edit/new screens?

Thanks! 

Joe

[Drrickryp]

Hi Joe, I don't think you need to use patch at al although you can use it. The reason you are creating a new item has to do with your patch command on second screen. In the Powerapps example, Patch( Customers, Defaults( Customer ), { Name: “Contoso” } ).  The defaults () is telling the DataSource to create a new record from your first screen.   Your second screen should be patching theis newly created record.  To do this you have to filter the DataSource for the record you just created, so the first two elements of the patch command should be Patch( Customers, First( Filter( Customers, Name = "Contoso" ) ),{Phone:  etc). 

An alternative to not using patch would be to start from scratch and then follow the example I give in the answer in powerusers.microsoft.com/t5/General-Discussion/Patch-function/m-p/140227#M48245.  I hope this helps 

[jcollins]

I thought the same thing... why do i even need patch anyway? Why won't clicking Save just save all the data on both screens?  Does my onSave need to be something special to do that?  I will check out your alternative now... 

[jcollins]

removing the Patch statement doe not save a record.  the form closes and that's it. 

[jcollins]

That didn't work either.... perhaps you missed the fact that I am using the "Customized form" which uses Sharepointintergration and has one form for new/view/edit screens.?   Yes, Defaults will create a new record, but then how do you also Edit a record without submitting a new record? Can Patch be used in an IF such that IF the form is New use Defaults but if it is in Edit mode use the patch(filter)? 

[v-xida-msft]

Hi @jcollins,

Could you please share a bit more about your scenario?

Do you want to update the existing record based on data within two screens when you edit the record?

If you want to update the existing the record based on data within two screens when you edit the record, please modify your formula within OnSave property of SharePointIntegration control as below:

If(
  !IsEmpty(SharePointIntegration.Selected),
  Patch('Credit Card Auth Form',SharePointIntegration.Selected,SharePointForm1.Updates,SharePointFormPay.Updates),
  Patch('Credit Card Auth Form',Defaults('Credit Card Auth Form'),SharePointForm1.Updates,SharePointFormPay.Updates)
);
ResetForm(SharePointForm1);
ResetForm(SharePointFormPay);
RequestHide()

Set OnNew propety of the SharePointIntegration control to following formula:

NewForm(SharePointForm1);NewForm(SharePointFormPay)

Set OnEdit property of the SharePointIntegration control to following formula:

EditForm(SharePointForm1);EditForm(SharePointFormPay)

Best regards,

Kris

[jcollins]

Hey, thanks @v-xida-msft!!

I think I am a lot closer now! This allowed me to edit an existing record without it making another record but now it just won't create that New record. The form just closes after I click Save but it never creates a record.  Is it looking for every field in the form to be empty?   On my 2nd screen, i do have a field that has default info pre populated. I will try to remove that and see but it would be nice to keep it. So maybe i can just check to see if another specific field is empty?  thanks for your help! 

PS: to clarify, i assumed OnView would be the same? ViewForm(SharePointForm1);ViewForm(SharePointFormPay)  - they were all set that way to begin with.

oh, to elaborate a bit more - I have the 2 screens that collect some data. 1st screen collects what the user wants and the 2nd collect their payment info.  The completed form is sent to Finance and they charge their credit card and come back to the form to check a box indicating that the card was charged (this triggers another flow to someone else). So, only screen 2 needs to be edited with that one yes/no check box.   My next thought was to just have a button in the form that only finance can see that OnSelect will patch that field with a Yes so that will trigger the next Flow.  

[jcollins]

Hey, thanks @v-xida-msft!!

I think I am a lot closer now! This allowed me to edit an existing record without it making another record but now it just won't create that New record. The form just closes after I click Save but it never creates a record.  Is it looking for every field in the form to be empty?   On my 2nd screen, i do have a field that has default info pre populated. I will try to remove that and see but it would be nice to keep it. So maybe i can just check to see if another specific field is empty?  thanks for your help! 

PS: to clarify, i assumed OnView would be the same? ViewForm(SharePointForm1);ViewForm(SharePointFormPay)  - they were all set that way to begin with.

oh, to elaborate a bit more - I have the 2 screens that collect some data. 1st screen collects what the user wants and the 2nd collect their payment info.  The completed form is sent to Finance and they charge their credit card and come back to the form to check a box indicating that the card was charged (this triggers another flow to someone else). So, only screen 2 needs to be edited with that one yes/no check box.   My next thought was to just have a button in the form that only finance can see that OnSelect will patch that field with a Yes so that will trigger the next Flow.  

UPDATE: FYI - removing the pre populated field data did not make a difference. also, putting paren around SharePointIntegration.Selected in the first patch did not make a difference. 

[jcollins]

Hey, thanks @v-xida-msft!!

I think I am a lot closer now! This allowed me to edit an existing record without it making another record but now it just won't create that New record. The form just closes after I click Save but it never creates a record.  Is it looking for every field in the form to be empty?   On my 2nd screen, i do have a field that has default info pre populated. I will try to remove that and see but it would be nice to keep it. So maybe i can just check to see if another specific field is empty?  thanks for your help! 

PS: to clarify, i assumed OnView would be the same? ViewForm(SharePointForm1);ViewForm(SharePointFormPay)  - they were all set that way to begin with.

oh, to elaborate a bit more - I have the 2 screens that collect some data. 1st screen collects what the user wants and the 2nd collect their payment info.  The completed form is sent to Finance and they charge their credit card and come back to the form to check a box indicating that the card was charged (this triggers another flow to someone else). So, only screen 2 needs to be edited with that one yes/no check box.   My next thought was to just have a button in the form that only finance can see that OnSelect will patch that field with a Yes so that will trigger the next Flow.  

UPDATE: FYI - removing the pre populated field data did not make a difference. also, putting paren around SharePointIntegration.Selected in the first patch did not make a difference.  

Seems like it is only going to look at the 'selected' record... is that the same as if I select New?

[v-xida-msft · Accepted solution]

Hi @jcollins,

As an alternative solution, please take a try with the following workaround:

Add two  buttons within the second screen -- "New Record" button and "Update Record" button.

Set the OnNew property of the SharePointIntegration control to following formula:

Set(IsNew,false);Set(IsEdit,false);NewForm(SharePointForm1);NewForm(SharePointFormPay);Set(IsNew,true)

Set the OnEdit property of the SharePointIntegration control to following formula:

Set(IsNew,false);Set(IsEdit,false);EditForm(SharePointForm1);EditForm(SharePointFormPay);Set(IsEdit,true)

Set the OnSelect property of the "New Record" button to following formula:

Patch('Credit Card Auth Form',Defaults('Credit Card Auth Form'),SharePointForm1.Updates,SharePointFormPay.Updates);ResetForm(SharePointForm1);ResetForm(SharePointFormPay);RequestHide()

Set the OnSelect property of the "Update Record" button to following formula:

Patch('Credit Card Auth Form',SharePointIntegration.Selected,SharePointForm1.Updates,SharePointFormPay.Updates);ResetForm(SharePointForm1);ResetForm(SharePointFormPay);RequestHide()

Set the Visible property of the "New Record" button to following formula:

If(IsNew=true,true,false)

Set the Visible property of the "Update Record" button to following formula:

If(IsEdit=true,true,false)

When you save a new record, please click the "New Record" button, when you edit a existing record, please click the "Update Record".

Best regards,

Kris