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.
As one of the system admins, it is absurd to me that I cannot view or have access to all of the items created in my organization. We have over 11,000 reports, sheets, and dashboards and I can't see them. I have no visibility to if people are using our plan for their own personal use, or what kind of work is going on unless…
I noticed this the other day and tested Ctrl + M – it does not work. I submit ticket to Smartsheet support – they told me that’s expected behavior because it’s not currently available even though it still shows as keyboard shortcut in the menu🙄 and told me to submit new product idea. Please add this keyboard shortcut to…
Currently, when using Automation to send Update Requests, there is no way to enforce mandatory (required) fields for users completing the request. This creates data quality issues, as users can submit incomplete updates, even when certain fields are critical. Proposed Enhancement Add the ability to mark specific fields as…
