Forum Discussion

MichelleCoslet's avatar
MichelleCoslet
Qrew Assistant Captain
7 years ago

Save as a spreadsheet - disable features

We have a quoting app that our suppliers have access to. They are often times saving as a spreadsheet, sorting the data, entering pricing, then c/p into QB. Problem is they are forgetting that they sorted the data, so when they copy and paste back into grid edit in QB - everything is in the wrong spot. 

I would LOVE for them to be able to IMPORT the data back into QB - but i do not like that they could potentially change fields/ add fields/ import into the wrong spot, etc.

Is there a way to:
A) Restrict them from being able to sort the spreadsheet
B) Restrict them from being able to modify fields other than those required by them (price, stock, etc)
C) create a better solution? Other ideas for importing? 

Another program i use for a customer of ours allows us to export as a spreadsheet. Edit only the allowable fields. Save. Then when i upload the spreadsheet into the program it automatically fills the required fields on the form. I do not have to select which Field is populated with What data.

Thanks!
Data import and export
  • EvanMartinez's avatar
    EvanMartinez
    Quickbase Staff
    7 years ago
    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.