In testing with Tableau, we found that the ODBC connector doesn't expose data from the Sheet Summary reports. That really reduces the usefulness of the Summary for enterprise integration.
Sign in to see the current vote count, add your own vote, or leave a comment.
Ack! Thanks for posting this! I was starting to create a somewhat complex solution and was exploring the use of Sheet Summary fields and now I'll have to reconsider my plan.
I was hoping to use Sheet Summary fields to track the same sets of data between many (10+) sheets with vary different purposes.
Spit-balling ideas..... I'll have to either make an entire column in the sheet report this data (and I'll lose some planned functionality) or I'll have to use some kind of an aggregate sheet that references each sheet's summary fields and then use the ODBC connector on that sheet. It would be a lot easier if the connector could do it natively.
Although we are extremely proficient when it comes to reducing load on our smartsheets (we use pivot, data mesh and data shuttle extensively), we still find ourselves hitting capacity limits (mostly because of the number of columns in conjunction with some pretty complex formulas). Breaking up data between sheets and…
Be able to print and/or export Workflow Automations in PDF and/or export to Visio. this would be used for document control and troubleshooting aid
It would be beneficial to be able to leverage Smartsheet Automations to make REST API calls. This has many potential use cases, but one I could see is adding users to Smartsheet groups when the are added to a 'roster sheet' in Smartsheet. It would allow us to use the full power of Smartsheet's API within easy to use…
