Form gets RANDOM DATA upon submission

[Anonymous]

Hi

I've been experiencing a very strange issue and have been trying to fix it for a couple months now, withouth success.

I have an app which reads/edits/creates records in a Sharepoint list.

The app is based on an automatically generated template and uses forms.

The form for editing/creating of course has a submit button.

This is what happens:

 . The user fills out the form with new data.

 . The user submits the form

 . The data is correctly inserted into the correct record in the SP list

 . While submitting the data and BEFORE the ONSUCCESS event is triggered, THE FORM DATA AUTOMATICALLY CHANGES. THE FORM GETS FILLED WITH DATA FROM A PREVIOUS RANDOM RECORD. The wrong data is coherent as it all belongs to the same record.

 . There are a number of things that need to happen OnSuccess, like sending email notifications, and all those actions get messed up because the data in the form is no longer correct!!

I disabled the automatic navigation to the start page so it's pretty easy to see the form fill itself with incorrect data after hitting submit and I could easily make a video of it. Let me know if that's necessary.

What could be the reason behind this behavior?

[v-xida-msft]

Hi @Anonymous ,

Do you customize a form in your SP List using PowerApps?

Could you please share more details about the formula typed within the OnSuccess property of the Edit form? Do you reference the data card values from the Edir form in the OnSuccess property?

Based on the issue that you mentioned, I have made a test on my side, and don't have the issue that you mentioned. On your side, please consider use Patch function to submit your form data instead of the SubmitForm function.

Set the OnSelect property of the "Submit" button to following:

If(
   IsBlank(SharePointIntegration.Selected) || IsEmpty(SharePointIntegration.Selected),
   set(CurrentSubmittedRecord, Patch('YourSPList', Defaults('YourSPList'), SharePointForm1.Updates)),// Store the submitted record into a variable
   Set(CurrentSubmittedRecord, Patch('YourSPList', SharePointIntegration.Selected, SharePointForm1.Updates))    
);
ResetForm(SharePointForm1);
...

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

Refresh('YourSPList');
Set(CurrentSubmittedRecord, Blank());
NewForm(SharePointForm1)

If you want to reference the submitted record value from the Edit form within the OnSuccess proeprty, you could consider reference the column value of the submitted through the CurrentSubmittedRecord variable as below:

CurrentSubmittedRecord.Column1

CurrentSubmittedRecord.Column2

CurrentSubmittedRecord.Column3

...

...

In addition, if you also want to populate the Edit form after you submit the form data, please consider populate the corresponding data card value through above CurrentSubmittedRecord variable. Set the Item property of the SharePointForm1 to following:

If(
  !IsBlank(CurrentSubmittedRecord),
  CurrentSubmittedRecord,
  SharePointIntegration.Selected
)

Best regards,

[Anonymous]

Hi @v-xida-msft 

  Do you customize a form in your SP List using PowerApps?

What do you mean by that?

I do reference the form and the user input in my onsuccess code. I think it'd be pointless to upload the code, as there are three Office365Outlook.SendEmail() commands which are quite long and complex, but not really relevant. 
At the end I'm using NewForm() to reset, and Navigate() to get back to the first page.

What is this?

SharePointIntegration.Selected

It's not recognized by my app. 

I'm using the Sharepoint connector to fetch and save the data.

I also have no idea where "the OnNew property of the "SharePointIntegration" control" might be.

I'd also like to corroborate with more information:

- the ResetForm() command does not reset the form. The first time it's used, it fills the form with data from a previous record instead. If it's used again, nothing more happens.

- the NewForm() command instead actually blanks the form.

Thank you for your help

[v-xida-msft]

Hi @Anonymous ,

Do you create a standalone canvas app based on your SP List or customize a form in your SP List using PowerApps?

If you created a standalone canvas app based on your SP List, please consider take a try with the following workaround:

Set the OnSelect property of the "Submit" button to following:

If(
   EditForm1.Mode = FormMode.New,
   set(CurrentSubmittedRecord, Patch('YourSPList', Defaults('YourSPList'), EditForm1.Updates)),// Store the submitted record into a variable
   Set(CurrentSubmittedRecord, Patch('YourSPList', BrowseGallery1.Selected, EditForm1.Updates))    
);
ResetForm(EditForm1);
...

Set the OnSelect property of the "+" icon/button to following:

Set(CurrentSubmittedRecord, Blank());
NewForm(EditForm1);
Navigate(EditScreen1)

If you want to reference the submitted record value from the Edit form within the OnSuccess proeprty, you could consider reference the column value of the submitted record through the CurrentSubmittedRecord variable as below:

CurrentSubmittedRecord.Column1

CurrentSubmittedRecord.Column2

CurrentSubmittedRecord.Column3

...

...

On your side, you could reference the column value of submitted record within your Office365Outlook.SendEmail() formula using above formula.

In addition, if you also want to populate the Edit form after you submit the form data, please consider populate the corresponding data card value through above CurrentSubmittedRecord variable. Set the Item property of the EditForm1 to following:

If(
  !IsBlank(CurrentSubmittedRecord),
  CurrentSubmittedRecord,
  BrowseGallery.Selected
)

Please consider take a try with above solution, then check if the issue is solved.

Best regards,

[Anonymous]

Hi

thank you for your help. 

By using the patch() function instead of the submit() function, I was able to pin point the issue: the form changes to different data because of the ResetForm() function. If the form is not resetted then the problem does not exist. Is it a bug in RESETFORM()?

The OnReset property is set to "false".

I tried applying your solution anyway:

- GOOD: using patch() the data gets correctly saved to the list (this also worked with submit)

- GOOD: using the CurrentSubmittedRecord global variable I'm able to reference the correct data

- BAD: the OnSuccess event is not triggered anymore. Do I need to use some code like this? 

If(!IsBlank(CurrentSubmittedRecord) && IsEmpty(Errors('my-list')), .... )

[v-xida-msft · Accepted solution]

Hi @Anonymous ,

The Patch fucntion would not fire the OnSuccess property of the Edit form, only the SubmitForm function could fire the OnSuccess property of the Edit form.

As an alternative solution, you could consider move the formula from the OnSuccess property of the EDIT form after the Patch function. I agree with your though almost, you could type these formulas within the If function as you mentioned:

Patch(...);
If(
    !IsBlank(CurrentSubmittedRecord) && IsEmpty(Errors('my-list')), 
    "Type your previous OnSuccess formula here"
)

Please take a try with above solution, check if the issue is solved.

Best regards,

[Anonymous]

Ok, the workaround works fine.

Still, is this an expected behavior, a known issue or a new bug?

[Anonymous]

I stand corrected. This work around causes other another problem, which took me ages to recognize. 
https://powerusers.microsoft.com/t5/Building-Power-Apps/SP-connector-unable-to-retrieve-all-of-the-d...

In short, when you edit a record, the versioning-enabled fields will appear to be empty after the edit if you don't make any changes to them. 

This is because: 

---

@Anonymous wrote:

The app will always display the last recorded input in the field. 

So if I edit a record and change some other field, but NOT the versioning-enabled field, then the new data committed to the list will be null for that field. For example, if the field "problem" is versioning-enabled:

A record: { ticket: 1; description: "blabla"; problem: "this&that" } 

Edited record: { ticket: 1; description: "blabla & bla"; problem: "this&that" } 

Data to commit upon submit: { ticket: null; description: "blabla & bla"; problem: null }

this is not a problem for the field ticket, but it is for the field "problem". Now the latest version of "problem" = null, and the app finds nothing more to display. 

---

To fix this, I need to change this piece of code so that it will not submit anything for all the fields where the updates are null.

If(
   EditForm1.Mode = FormMode.New;
   // IF NEW FORM: Store the submitted record into a variable
   Set(CSR; Patch('helpdesk-ticketing'; Defaults('helpdesk-ticketing'); EditForm1.Updates));
   // IF EDITING:
   Set(CSR; Patch('helpdesk-ticketing'; 'lista-ticket'.Selected; EditForm1.Updates))
)

In other words, I need to rebuild EditForm1.Updates as a collection of actual updates.

Could you please help with that?

EDIT: testing proved that this problem is unrelated