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?
Solved! Go to 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,
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,
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
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,
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')), .... )
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,
Ok, the workaround works fine.
Still, is this an expected behavior, a known issue or a new bug?
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
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!
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
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.
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