Protecting Editable Fields - Best practice
At our school teachers enter a lot of data and we want to protect ourselves from accidentally clicking or tapping and modifying a fields. Here are a few thoughts on how I am thinking of making this possible. I'd love to get some feedback on which make more or less sense:
(1) Initially I thought I have one tab that only has functions displaying the data from the editable fields but on phone tabs show up sequentially which would work.
(2) Using a different view, one that has all the editable fields and another only displaying them via function fields.
(3) Having at the top of each tab a toggle which will switch all fields from editable input fields to equivalent function fields for view only purposes.
Which of these or other options would you guys consider to be a good implementation of protecting fields? Any and all thoughts are much appreciated!
12 replies
-
Halio,
I would go for option 3 , but I would make use of the field option 'writable if' in combination with a Yes/No field to protect those fields from input instead of using an extra equivalent function field.
Steven.
-
Oh man, of course, thank you for your suggestion Steven!
I have to manually add my toggle reference to each fields' "writesble if" field or is there a way to make it apply to multiple fields to speed up the process? -
Is there any way to have the edit toggle reset when I close or open a record?
-
the addition of using buttons on top of the toggle is a great UI addition that Leonard shared https://ninoxdb.de/en/forum/technical-help-5ab8fe445fe2b42b7dd39ee7/button-to-show-fields-5b51c4920eb4ca611f2e2365
-
You can make the whole table also "writable if"....
-
Good idea Steven, I'm just not sure how I can toggle a condition to make records writable or not. Could you give me an example?
-
Sure,
Let's say we make use of a seperate table for settings with only one record called SETTINGS and a Yes/No field called EDITTABLE.
Then you can put this in the "writable if" section of the desired fields you want to protect in the other tables.
record(SETTINGS,1).EDITTABLEFolow this thread for an example database: https://ninoxdb.de/en/forum/use-cases-5abd0b9c4da2d77b6ebfa395/create-tables-with-autonumbering-with-ease.-5d5ee82ab6ba1f2dab0664b4
Steven.
-
That's brilliant Steven. Could I also create a multiple choice field that refers to users and easily add or remove users from being able to edit a table?
-
Which version do you use? If it's the cloud (thus web) it's better to use the build in user roles. Else if it's a stand alone version (Ipad,Mac), you will need a sort of login screen first with an optional password to know which user is using the database I think?
I'll try to post an example in the weekend... If Nick is not first
, we'll see... 
Steven
-
I'm using the cloud version only for our school.
-
@Steven, I missed that one...
LOL
-
RoSoft_Steven Rooryck
Works Greats to protect field , for me much better to protect the Plan Dates and don't move for error in the Gantt Chart.
Content aside
- 3 yrs agoLast active
- 12Replies
- 2833Views
-
1
Following