Forum Discussion
EvanMartinez
7 years agoModerator
Hi Murali,
Currently a report can be saved as a CSV by using the option to Import/Export or 'Save as Spreadsheet' under the More dropdown on a table report. 'Save as Spreadsheet' will jump right to creating a CSV to download. Either will allow a user to pull the data from a Quick Base table into a CSV. Out of curiosity is there something about the two options under the More dropdown that make them undesirable for your use?_
Currently a report can be saved as a CSV by using the option to Import/Export or 'Save as Spreadsheet' under the More dropdown on a table report. 'Save as Spreadsheet' will jump right to creating a CSV to download. Either will allow a user to pull the data from a Quick Base table into a CSV. Out of curiosity is there something about the two options under the More dropdown that make them undesirable for your use?_
_anomDiebolt_
7 years agoQrew Elite
This is the feedback you should pass along:
QuickBase staff is collectively obsessed with use case analysis and hard-coding features that have limited ability to be further customized by the end user. Users want general capabilities that can be customize to their individual snowflake needs no matter how cosmetic or complex.
But user's individual requests often go unaddressed because the feature is viewed as non-critical and never crosses the popularity threshold so that marketing and product managers commit to developing the feature. It is all about the long tail today.
Every GUI ease of use feature you develop should have an analog that can accomplish the same thing through an API and script automation. You need functional parity between the "clicks not code" and "code not clicks" memes. Without greater support for APIs and script you are locking your users out of the using the cornucopia of features that are coming through browser innovations. QuickBase should view all the innovations that are jammed into browsers today as economic externalizes that someone else paid for developing.
QuickBase staff is collectively obsessed with use case analysis and hard-coding features that have limited ability to be further customized by the end user. Users want general capabilities that can be customize to their individual snowflake needs no matter how cosmetic or complex.
But user's individual requests often go unaddressed because the feature is viewed as non-critical and never crosses the popularity threshold so that marketing and product managers commit to developing the feature. It is all about the long tail today.
Every GUI ease of use feature you develop should have an analog that can accomplish the same thing through an API and script automation. You need functional parity between the "clicks not code" and "code not clicks" memes. Without greater support for APIs and script you are locking your users out of the using the cornucopia of features that are coming through browser innovations. QuickBase should view all the innovations that are jammed into browsers today as economic externalizes that someone else paid for developing.