A safer way to save an object key as an edit?

Question

I always have concerns about simply storing an entity key using hidden input in my views. It’s too easy even for an inquisitive user to edit this value in the browser console and, possibly, ultimately update the object that this user should not have access to.

Is there a possible way to keep this value in the views without adding too much encryption complexity, etc.?

Answer 1

Save it in javascript variable. Then create a js function in postback and make the most appropriate use of it there (if you use AJAX postbacks, this should be easy;))