This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Unless Im missing it, I would like the ability to lock changes to fields in a base and/or records. Would help prevent accidental deletion. I discovered several days later I had done thisโฆ
I would love to be able to lock some fields as well ! So that my employees would be able to modify and use my template without changing the multiple select possibilities of my field.
+1
Even when I use the database myself, I occasionally find me entering a value that is not in the list. The field will accept it obviously as a new value. I donโt want that. I would either like to see a message that this value is not in the list, or even better: having the ability to lock the values.
+1 vote from me. We also have a set price guide that should not have any changes made to it. I am new to AirTable and loving it. I understand you canโt lock a record. Can a full table be locked?
+1
Our use case is we have a huge list of Thing A with counts and a bunch of manually-created categories, and a second table of Thing A we use to paste in updated counts (because thatโs the only data being updated and we donโt want to disturb all the other fields, especially our hard-won categories). When we paste in the list of current Thing Aโs and their counts to the update table, any new unique Thing Aโs transfer over to our main table, and the new counts transfer as well. Thatโs good! But this week someone got confused, and pasted the new Thing Aโs directly into the main table, and since they were in a different order, they wiped out the connection between the Thing Aโs and their proper categories. So basically we would like for the Thing A field in our main table to be open to the creation of new rows of data, but locked to overwriting of existing rows. Even better would be if this were variable by person or role.
Exactly โ infinite use cases for this. Iโm tracking submissions, by person and company. After a submission has been made โ I need it saved forever. If a person changes companies, or if a company changes through Acquisition or merger โ I need to be able to update my tables without it changing the Submissions records.
We collaborate across multiple teams/departments and I would love the ability to lock down Single/Multiple selects so other users are not allowed to add more Options and only use the available selects.
+1 again, accidental deletions are a real problem for our team. Iโd like to be able to lock to prevent accidental deletion and make sure additions and edits are purposeful. For a given field, Iโd like to set โlockโ that requires a simple โunlockโ button to edit.
