cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Unsaved Property of Edit Form Is Always True

The Unsaved property of my Edit Form form always has a value of true, even when I have made no changes. My form is in FormMode.Edit.

 

As a test I created a button with this code in the OnSelect property.  The Edit Form still shows Unsaved as true after I click the button

 

ResetForm(Form1);

 

 

---
Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up." 

30 REPLIES 30

I see that we're 6 months later, and still no fix, or even a response from Microsoft....

 

Just to let you all know that I'm still having major issues with Form.Unsaved - it is simply not usable.

 

@v-bofeng-msft - Please can we have some sort of response from Microsoft?

 

James.

 

 

appyourdata
Frequent Visitor

Hi guys,

 

I think I found a possible workaround. I included a ResetForm(FormWithTheIssue) on the Onvisible of the screen where the form is located.

 

That seems to have fixed my issue.

 

Hope it helps

 

Manuel

biterbit
Kudo Commander
Kudo Commander

I don't think that a form reset is a universal solution. Having hit this issue, I added a button with an OnSelect property of ResetForm(formName) and the form's Unsaved property remains true . My experience is that loading a record into a form sets the Unsaved property to true, and this remains even after a form reset. The Unsaved property is only set to false when the form is first in New mode.

One thing I've notice that can cause the .Unsaved property to not behave as expected is default values.  This is because after the form is loaded it sets the defaults.  If these defaults differ from what is stored in the data source (SharePoint in my case) then it will consider the data changed.  Ultimately, I believe the .Unsaved property is only triggered when something on the field on the form differs from what is in the database and that by coding things certain ways you can have unintended consequences that cause this to happen.

 

The best solution to avoid this is to move away from the use of form using the Submit command and move to using Patch, which will give you much more control over when things are determined as Saved or Not Saved as well as other aspects of programming in PowerApps.  While I still use forms occasionally, it is when I just want to do something quick.  Anything that is going to be a long term solution for users I believe you'll want to migrate or start with the Patch method of saving your data.  Doing so will save you a lot of headaches.  Not to mention it is much easier to change your data source from say Sharepoint to SQLServer using this instead of the Form with Submit.

 

Hope this helps,
Steve

I posted this above as a reply, but meant it for you: 

One thing I've notice that can cause the .Unsaved property to not behave as expected is default values.  This is because after the form is loaded it sets the defaults.  If these defaults differ from what is stored in the data source (SharePoint in my case) then it will consider the data changed.  Ultimately, I believe the .Unsaved property is only triggered when something on the field on the form differs from what is in the database and that by coding things certain ways you can have unintended consequences that cause this to happen.

 

The best solution to avoid this is to move away from the use of form using the Submit command and move to using Patch, which will give you much more control over when things are determined as Saved or Not Saved as well as other aspects of programming in PowerApps.  While I still use forms occasionally, it is when I just want to do something quick.  Anything that is going to be a long term solution for users I believe you'll want to migrate or start with the Patch method of saving your data.  Doing so will save you a lot of headaches.  Not to mention it is much easier to change your data source from say Sharepoint to SQLServer using this instead of the Form with Submit.

 

Hope this helps,
Steve

Matren
Super User
Super User

Hello Folks and @mdevaney @WarrenBelz ,

 

It's 2023 and I came across the same issue. I would love to use the Unsaved property to detect whenever a user makes changes to a field when editing a form; however, the Unsaved property remains True for me as well. Thus, I'm searching for workarounds without having to redesign the whole application.

 

Use Case: Do not allow the form to be saved without the user making a change to a field. If the user enters changes to a field, then a submit form icon will appear. Currently I have 70+ fields all with different data validation. 

 

Thoughts? 

So yes, now its March 2023 - 2 Years since my last post on this subject!

 

and Yes, guess what - the Form.Unsaved property is still a huge BUG, and I never use it.

 

My current standard process is to add a Toggle (set to invisible) and set a giant formula in the Toggle.Default property. I then use Toggle.Value to see if the Form needs saving or not.

 

Not ideal at all, but I've gotten used to it now, and can actually be really helpful when debugging issues!

 

James.

Matren
Super User
Super User

Hi @james_hathaway,

 

Yes, reading through the messages this continues to be an issue. From the other posts above, I did investigate the default property for my fields, and they do contain code that I need for my app to work. So there are cases when the default property is different than what is in my datasource.

 

Instead of using the default property, it would be nice if there was a property that would compare the Selected record's fields to the current data card values, and if any are any differences then the property would change from false to true. Like you, I now have to write a large amount of code, and stick it in the DisplayMode for my Save button, disabling it to prevent the user from saving the form with no changes. Otherwise, when a user reviews the version history showing changes for a form, it is confusing that there are different versions with no changes. 

 

I'm waiting for a few more responses, but I would recommend submitting this as an idea so it can be voted upon and enacted by Microsoft.

 

Best,

Matren

Hi Matren,

 

When you say you'd like:

 

"a property that would compare the Selected record's fields to the current data card values, and if any are any differences then the property would change from false to true."

 

You mean a function like "Form.Unsaved" ?

 

Yes - it would be really nice if PowerApps had a function like that....

Hi @james_hathaway, Yes, exactly.

 

Hi @mdevaney , @WarrenBelz , @biterbit , @subsguts ,@sguthrie1, and everyone,

Apparently, an idea has already been created for this issue!

 

Please click the link to vote for it!

https://ideas.powerapps.com/d365community/idea/7f43c858-66a5-4365-8d85-a3b5d578457f

 

Thanks,
Matren

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

Top Solution Authors
Top Kudoed Authors
Users online (2,781)