This is for day to day non power users - ie that cant write code, don't have access to sql. For example, a non technical team who says 'hey what devices of XXX model do we have and what are their serial numbers'. This is the most common thing.
They won't know json, won't know api, and right now copy/paste HTML tables and try really hard to get them to get formatted properly in excel or libreoffice.
My thought is generally that if there is already a sql query to build the table, couldnt the same sql query be tied to an 'export' button that instead of displaying a table, just downloads a CSV?
This is for day to day non power users - ie that cant write code, don't have access to sql. For example, a non technical team who says 'hey what devices of XXX model do we have and what are their serial numbers'. This is the most common thing.
They won't know json, won't know api, and right now copy/paste HTML tables and try really hard to get them to get formatted properly in excel or libreoffice.
My thought is generally that if there is already a sql query to build the table, couldnt the same sql query be tied to an 'export' button that instead of displaying a table, just downloads a CSV?