Unanswered

App form always showing Unsaved since Studio version 3.25043.10

(1) Share

Report

Posted on by biterbit

406

I have a form which has not changed in several months that, since I last published the app, is now reporting as Unsaved as soon as it is loaded. After fruitless attempts to track down the cause, I reverted from Studio version 3.25043.10 to 3.25041.10, and the problem went away. As this earlier version might not be around much longer, has something changed in the way form updates are handled or is this a bug to be fixed in a later Studio release?

Categories:

Building Power Apps

I have the same question (0)

All responses (5)

Answers (0)

BCBuizer 22,505 Super User 2025 Season 2 on at

Like (0)

Report

Hi @biterbit,

There seem to be more issues recently with modern controls in that got resolved by changing authoring versions:

power apps issue with modern controls checkbox in gallery not showing checked

Solved: Modern Component Errors

On the part where the stable authoring version will not be around forever: as long as you don't publish your app again, it will continue running on the current authoring version and will not cause issues. In case you don't have that luxury and you want more control over the issue getting resolved, I suggest you raise a ticket with Microsoft: Support requests | Power Platform admin center

Was this reply helpful? Yes No
ronaldwalcott 3,847 Super User 2025 Season 2 on at

Like (0)

Report

If you are referring to using modern controls in forms with the form.unsaved property then some people have highlighted this behaviour as a bug.

Was this reply helpful? Yes No
biterbit 406 on at

Like (0)

Report

@ronaldwalcott and @BCBuizer: The forms do not use Modern Controls so I think I will wait until I next need to do a release and, if the problem persists, contact Microsoft. Thanks for your inputs.

Was this reply helpful? Yes No
biterbit 406 on at

Like (0)

Report

After creating a new app, I can reproduce this issue by switching between Studio versions 3.25041.10 and 3.25044.10. I have raised a support ticket with Microsoft.

Was this reply helpful? Yes No
biterbit 406 on at

Like (0)

Report

After escalating this to Microsoft, I have been told that this is expected behaviour. Their explanation is that a datacard for an empty text field will always report as Unsaved = true, because the datacard's Update and Default properties report an empty value differently: one returns an empty string ("") and the other returns Null. It's not clear from their reply whether this behaviour can be changed but they insist that an empty text field is, by definition, unsaved.

Was this reply helpful? Yes No