cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
ck25415
Post Patron
Post Patron

Avoid clearing the data in form after submitting data using Patch

Hello,

 

I have declared a variable on screen visible using Set(currentRecord, Defaults('datasource')), datasource is a sharepoint list.

I have a  timercontrol on the same screen with onTimerEnd set to Set(currentRecord,Patch('datsource',currentRecord,EditForm1_MemberSubmission1.Updates,EditForm1_MemberSubmission2.Updates)). The two editforms are on two different screens. After submitting the data to sharepoint list, the text in the fields is cleared which I am trying to avoid so that user can continue to see the submitted text.

 

Thanks,

1 ACCEPTED SOLUTION

Accepted Solutions
v-xida-msft
Community Support
Community Support

Hi @ck25415,

 

Could you please share a screenshot of your app's configuration?

Further, could you please show more details about the Timer control within your app?

 

I have made a test on my side (using a Button control instead of a Timer control), and don't have the issue that you mentioned. The GIF screenshot as below:Test1.gif

 

 

Please check if you have reset the Edit forms within your app using ResetForm function after you submitted the data. 

 

In addition, please take a try to add a Button control within your app instead of the Timer control to submit the form data, then set the OnSelect property of the Button control to following formula:

Set(currentRecord,Patch('datsource',currentRecord,EditForm1_MemberSubmission1.Updates,EditForm1_MemberSubmission2.Updates))

then check if the issue is solved.

 

Please also check if the Item property of the Edit forms set to the currentRecord variable, if yes, please remove the currentRecord variable from the Item property of the Edit forms (Remain empty within the Item property of the Edit form control). 

 

 

Best regards,

Kris

 

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.

View solution in original post

5 REPLIES 5
nickduxfield
Continued Contributor
Continued Contributor

Check your gallery to ensure any filters don't filter out on success.
Check the on success property of the form to ensure it doesn't reset form.
Check the form reset property.
You need to set global variables on App start.
Use the on success property of your form to capture last submit with form.lastsubmit.field.

Some ideas...
nickduxfield
Continued Contributor
Continued Contributor

Apologies, are u using the form, or a form you created?
If so,
You can make use of a tempcollection.of preferably on app start collect(tempcollection, first(source().
Put a switch on new, or edit or view button.
New, set defaults,
Edit, patch(tempcollection,first(tempcollection),this item) or clear collect.
On submit, if new, collect(source, first(tempcollection))
If edit, patch(source, from tempcollection)
Set defaults on all fields to first(tempcollection).field1

Ask if needed

Hello Nick,

 

I am using the editform(defualt set to new) which loads with the screen(not creating a new item from the screen). I checked the onsuccess and reset properties which was set to false. I did not quite understand the tempcollection you explained, could you please explain it more.

 

Thanks much,

 

@xample@ck2541

If I understand now,

You have the form with datacard OODB, and you havent created a your own with controls. Reading your history, you were using patch for unique fields which led me off track.

Regarding your choice of default form mode of NEW, is this on purpose?

If so, I can deduce the following:

The form item property is usually paired to a gallery as gallery.selected, if you select an item in the gallery to edit and submit the form, it will still show gallery.selected and the fields will be populated.

However, if you have the mode set to NEW form, gallery.selected is ommitted because its not in the gallery yet, and therefore the form will be empty on submit.

 

My next thoughts are, your default form mode of NEW.

Other thoughts are, do you just want to see the last submit? Or use the last submit in the populated fields on the next submit?

 

To get around this you might want to try, creating a temp collection.

Try to collect the last(Source) into a collection with the aim of only 1 record.

A few methods:

  1. For the submit button, patch to this temp collection as in First(Tempcollection,{Form.Lastsubmit....}), or similar.Then for the default / update for each datacard depending on what the reason for the Default as a NEW form is, set to the First(tempcollection).field.
  2. On Success of the form, patch to this temp collection as in First(Tempcollection,{Form.Lastsubmit....}. Then put in the item property of the form First(Tempcollection)

Example: Title: First(Tempcollection).Title

This will ensure you will always see the last submit, and if it fails, you will have a draft.

When you go to edit, ClearCollect(tempcollection,thisitem) or similar. If new, you can also decide defaults etc.

 

If im off track let me know.

I prefer to use minimal variables in all my solutions. My default option is to use collections where possible be cause you can easily modify collections as apposed to variables.

v-xida-msft
Community Support
Community Support

Hi @ck25415,

 

Could you please share a screenshot of your app's configuration?

Further, could you please show more details about the Timer control within your app?

 

I have made a test on my side (using a Button control instead of a Timer control), and don't have the issue that you mentioned. The GIF screenshot as below:Test1.gif

 

 

Please check if you have reset the Edit forms within your app using ResetForm function after you submitted the data. 

 

In addition, please take a try to add a Button control within your app instead of the Timer control to submit the form data, then set the OnSelect property of the Button control to following formula:

Set(currentRecord,Patch('datsource',currentRecord,EditForm1_MemberSubmission1.Updates,EditForm1_MemberSubmission2.Updates))

then check if the issue is solved.

 

Please also check if the Item property of the Edit forms set to the currentRecord variable, if yes, please remove the currentRecord variable from the Item property of the Edit forms (Remain empty within the Item property of the Edit form control). 

 

 

Best regards,

Kris

 

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.

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