Forum Discussion
EvanMartinez
7 years agoModerator
Hi Mkosek,
I can confirm that there is not a native option available in Quick Base to lock down a spreadsheet generated from a Quick Base table to prevent it from being sorted. Once it is exported as a CSV it is available to be opened by other programs and manipulated like a normal CSV, special restrictions aren't put in place to the CSV. For restricting what fields they are able to modify that is possible by controlling their field access via the role they are using to access Quick Base. If I want them to be able to see 15 fields but only edit 3 of those fields I can set permissions on those 3 fields to modify and then the other fields can be set to view only. This allows them to view and export the full report of 15 fields but upon import only those 3 fields are available to be imported into. They would need to select the correct fields to import into, so that part of the process is still reliant on them.
For the import they also would only be given the option to create a new field if they have administrative permissions in that application or table. Otherwise they simply have the choice to import into an existing field or not import in that column of data. I hope this information is helpful.
I can confirm that there is not a native option available in Quick Base to lock down a spreadsheet generated from a Quick Base table to prevent it from being sorted. Once it is exported as a CSV it is available to be opened by other programs and manipulated like a normal CSV, special restrictions aren't put in place to the CSV. For restricting what fields they are able to modify that is possible by controlling their field access via the role they are using to access Quick Base. If I want them to be able to see 15 fields but only edit 3 of those fields I can set permissions on those 3 fields to modify and then the other fields can be set to view only. This allows them to view and export the full report of 15 fields but upon import only those 3 fields are available to be imported into. They would need to select the correct fields to import into, so that part of the process is still reliant on them.
For the import they also would only be given the option to create a new field if they have administrative permissions in that application or table. Otherwise they simply have the choice to import into an existing field or not import in that column of data. I hope this information is helpful.