I use SaveIcon.Visible = MyForm.Unsaved, to show the SaveIcon when MyForm has unsaved chages. This works well, as long as I don't have a Lookup field on the form. As soon as I add a (standard/not-customized) Lookup, MyForm.Unsaved seems to be always true, e.g. the SaveIcon is always shown. Am I doing something wrong, or should I somehow customize the Lookup card, or ... ?
Cheers for any suggestions,
Is it an edit form? What is your data source?
I am having a similar issue as well.
I have a gallery connected to a sharepoint list. Next to the gallery, I have an editform (like a properties pallette). I would like to disable the gallery if there are any changes in the form.
Using form.unsaved seems to be unreliable. Freshly loaded items appear unsaved without any interaction.
I am going to try and find another way to determine if the form has changed...
I have the same problem with some forms. I have one form with two textboxes, two person lookup fields and two other lookup fields. The unsaved flag is always true without any interaction.
I have also had this problem on pretty much EVERY PowerApp I have created - it seems that the Form.Unsaved Property is pretty much useless beyond the simplest of forms.
In my latest project, I am independently updating the record shown in the Form with a Patch function, and then using ResetForm to ensure the form shows the newly patched value, and guess what - the Form.Unsaved is true. For a newly loaded form/record.... Crazy huh?
Is anyone from the Microsoft PowerApps Team looking at this thread?
Is it possible to have an update on the resolution of the buggy Form.Unsaved function?
Featuring samples like Return to the Workplace and Emergency Response Applications
We're excited to announce our first cross-community 'Can You Solve These?' challenge!
Reopen responsibly, monitor intelligently, and protect continuously with solutions for a safer work environment.
We are excited for the next Super User season.
Features releasing from October 2020 through March 2021