top | item 34811040

(no title)

If that's working, great!

Few differences I'd call out:

- If you have summary tables with formulas we'll auto-extend those tables as we see new periods in your data. e.g. If you have "revenue by month" calculated using SUMIFs on top of charge data and we see a new month, we'll copy your formulas down/across.

- Any charts based off those tables will also update. Sheets doesn't do either of these things.

- Finally, people who've switched from Sheets have found our query UX to have much tighter iteration loops by being more deeply integrated into the product.

discuss

user3939382|3 years ago

I'm pretty sure I can get the updates to work (right now it's based on synchronous UI) just because Sheets has auto recalc and event trigger features. However I'd say it is different than your product since my strategy is very low level.

I'm using a JavaScript interface to JDBC. It's left to the developer to find this scripting system (GAS), stitch the pieces together, figure out where the Google vs JDBC docs connect, etc. Getting auto-complete and syncing in my IDE was a lot of work and research. Google has their own sync tool which is basically a git work-a-like that you have to use in tandem with git.

It's powerful but there's nothing friendly about it.

What is does have is -- all the users already know Google Sheets. So they have this big system they already know that they can use with the data my code populates. That includes all the export features Google Sheets has. Buy in from management is easy, since it's a platform everyone knows and we're already paying for it.

You have to weigh your tradeoffs.