Unanswered

Problem with Form.Unsaved if a Sharepoint Lookup field is contained

(0) Share

Report

Posted on by Community Power Pla... Microsoft Employee

Hello,

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,

Dennis

Categories:

Building Power Apps

All responses (13)

Answers (0)

Sort by

v-monli-msft Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Anonymous,

Is it an edit form? What is your data source?

Regards,

Mona
Community Power Pla... Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

It is an edit form and a SharePoint list with one lookup field is the data source.
Community Power Pla... Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

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...
Community Power Pla... Microsoft Employee on at

Like
a
(2)

Report
Copy link

Link copied!

It's a year later and I'm having the same issue with the Form.Unsaved property in Visible. Any updates?
ntokozos 6 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi am having the same issue has there been any resolution to this or alternative?
ntokozos 6 on at

Like
a
(0)

Report
Copy link

Link copied!

@Anonymous Did you find anything?
@Anonymous wrote:
I am going to try and find another way to determine if the form has changed...
ShAnc 26 on at

Like
a
(0)

Report
Copy link

Link copied!

I'm having the same issue. Would be nice to find a solution.
JohnP 543 on at

Like
a
(0)

Report
Copy link

Link copied!

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.
james_hathaway 427 on at

Like
a
(1)

Report
Copy link

Link copied!

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?

Thanks
James.
Spinner 124 on at

Like
a
(0)

Report
Copy link

Link copied!

Same here, just run into this problem. Form.Unsaved is always true, meaning it's close to unusable.