Replacing Sheets data connector

We're making connected sheets commonly accessible to G Suite Enterprise and G Suite Enterprise for Education clients. Connected sheets encourage you to dissect BigQuery information in Google Sheets. It was already accessible in beta. Connected sheets will supplant sheet data connector, an increasingly constrained approach to interface sheets and BigQuery. 

Why you’d use it

Connected sheets join Google Sheets to BigQuery, so you can analyze huge BigQuery datasets utilizing known spreadsheet tools and tasks. This implies clients don't have to know SQL and can create bits of knowledge with fundamental spreadsheet activities like equations, graphs, and pivot tables. 

This makes it simpler for individuals from your association to comprehend, collaborate and produce bits of knowledge from information. In particular, it can assist a subject with making a difference specialists work with information without depending on experts, who might be less acquainted with the setting of the information or be overloaded with a wide scope of information requests. 

Connected sheets incorporate all the capacities of the legacy sheets data connector with extra improvements. Improvements incorporate the capacity to examine and visualize information in sheets without expecting to initially extract the information, having the option to see a preview of information through a sheet, and scheduling information reinvigorates to abstain from breaking down stale information. 

What's for admins

No activity required, Connected Sheets will be ON by default. To use it, you must have set up BigQuery for your organization, and users must have access to tables or views in BigQuery.

What's for end clients

This feature will be ON by default. To utilize it, you must approach tables or views in BigQuery. 

Available to G Suite Enterprise and G Suite Enterprise for Education customers


Popular posts from this blog

Google Partner in Bangladesh

Refresh BigQuery data in Sheets using Apps Script and Macros

To run or not to run a database on Kubernetes: What to consider