Unanswered

Unsaved Not Working Consistently

(0) Share

Report

Posted on by Community Power Pla... Microsoft Employee

Hello,

I have an edit form with several types of cards. I have a button that submits the form. I want this button to appear when the form is in new mode, and when the form is in edit mode and there are unsaved changes to the form. I have 'frmForm.Unsaved' in the Visible property of the Submit button. This works for all the text input fields, the date dropdown field the yes/no toggle and one of the dropdown fields. For a second dropdown field it is not working. A diagnostic label I have that indicates true or false for frmForm.Unsaved does not change from 'false' when this one dropdown is changed, but it does change to true for all other edit fields. Any ideas as to what might be going on here? I can't find any significant difference in the attributes of the two dropdown fields, one of which works and the other which does not.

Any help would be most appreciated.

Categories:

Building Power Apps

I have the same question (0)

All responses (2)

Answers (0)

RandyHayes 76,299 Super User 2024 Season 1 on at

Like (0)

Report
Copy link

Link copied!

@Anonymous

This might be helpful for you...

The Unsaved property will be true whenever ANY field in your form has a scenario where the Default value of the DataCard does not match the Update property value.

A very common scenario is the the underlying data record has a blank value in it and you are setting the value to something else in the Update - even if it is an empty text (which is NOT the same as blank).

So, without seeing any of your formulas, I can only provide some general guidance, which is - check what the difference is between the Default property Value and the Update property Value on the datacard that contains the control that you are having issues with.

I hope this is helpful for you.

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Thanks Randy,
I will take your suggestion and look at Update v Default. I figure it must be something like this, or the malfunctioning field is corrupted somehow. If I can't fix it maybe I will remove and reinsert the card. Your response is interesting as it is good information to know regarding Unsaved. I have the opposite problem to the one you describe however, as this one miscreant field can change, but Unsaved still calculates as 'false'. Thanks @RandyHayes

Was this reply helpful? Yes No