BigQuery (beta)

Softr's BigQuery connection lets you unlock the power of your data warehouse like never before. Build custom dashboards, reports, and even full-fledged apps, all tailored to your business's specific needs.

Tailored reporting

Empower users with intuitive dashboards tailored to their specific roles. This enables them to track key metrics like user activity, application performance, and payment trends directly within the Softr workspace. For example, your team can easily build a comprehensive users and applications dashboard without complex analytics software.

External data sharing

Securely provide strategic insights to partners and vendors. For example think of yourself as an ecommerce platform that can now extract product performance data from your BigQuery warehouse and offer partners valuable dashboards highlighting how their products are performing.

This guide applies in case following errors or similar have been seen while users try to connect their BigQuery datasources to lists or charts:

The reason for these errors is that working with “external tables” in BigQuery requires additional permissions (OAuth scopes) that should be requested by us and will be prompted to user during authentication flow. However as we have already pretty broad permissions and adding more on top of it as a third party application might not create a good impression with customers, we decided not to ask for these additional permissions and instead present customers with some workarounds and other ways to fix this.

In BigQuery, while creating a table in some cases user can decide or has only the option to create an external datasource.

External tables are forced or available when user creates a table from:

if user goes for an external table in these cases, trying to integrate such table with Softr will give them an error message similar to those mentioned above.

To identify an existing table as either internal or external, one could take a look at table details and would see a “External data configuration” section for external tables similar to following:

One option as a workaround here is to make sure table type is set to Native table in the creation phase. This option is not available for all sources.

This will however mean that there will be no syncing happening with the original source and table will not be updated if/when that external source changes.

In case user has no other option, they can also create a second table that is native and copies all the data from the external table. User then might use that copied table in Softr. A pseudo SQL to do this is: create table native_table_copy as select * from external_table

This has the disadvantage that the space required for data will be duplicated.