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.
Problem Smartsheet environments quickly become cluttered with inactive Sheets, Reports, and Dashboards that are no longer viewed or updated. This creates confusion for users and significant overhead for admins, especially in large or regulated environments. There is currently no native way to automatically identify, notify…
Most customer's metadata houses their profile data, some from intake sheet and some either cell linked in or brought into metadata using formulas. Needs change after design and often the new data point needed comes from non-metadata templates, which can cause a blocker if methods used are those above. If it were possible…
Having the ability to auto-resize the Calendar App view based on the widget size is needed. We have a "Due in 7 Days' calendar for our dashboards and would like it to be anchored at the top right. Unfortunately, as currently designed, the calendar takes up a significant amount of space and must be moved to the bottom.
