Why does the "back" action unlock locked fields?

[Anonymous]

Is this by design or is this a bug?  If I lock a field as a developer, I don't want a user to be able to unlock it with the back button.

As a fix for my "back" button, I added actions that lock the field before and after the "back" action, so my back button actions look like this:

Lock Field _____

Back

Lock Field _____

[Colin-Albert]

Back just steps backwards through any fields selections made by the user in turn.

Lock and Unlock is just seen as any other selection so is included when you click Back and Forward.

If you want to force specific selections then use bookmarks, set expressions or alternate states.

[cesaraccardi]

If you save the application with the locked fields they will remain locked so the user won't be able to unlock them by clicking on the back button.

[Anonymous]

I need the field to be flexible.  I use triggers on the sheet activation to lock a field, but on exit I unlock that field.  I don't want it to be locked permanently, but only to stay locked while on that sheet.  But neither do I want a user to be able to unlock that field.

Thanks

[cesaraccardi]

I see, in that case I think you can get the same result using set analysis in the objects' expressions of that particular sheet. e.g. sum({$<LockedField={'Locked Selection'}>} Sales)