Google Sheets

Main article about Export/Import is here

Create Google Sheets DataSource

Open BGDatabase window Window->BGDatabase

Go to DataSources tab, press plus icon, chose Datasource type to be GoogleSheets and click Add button

[Important]: Keep your settings file private if you use GoogleSheets. Do not share it with anyone

Setting up Google Sheets DataSource

Setting up Google Sheets DataSource depends on authentication type. Chose authentication type and read setup guide for this type.
OAuth 2.0 (default) Service API Key Anonymous
Access Read/Write to all spreadsheets Read/Write to all spreadsheets Read-only to public/shared spreadsheets Read-only to public/shared spreadsheets. No access to input value
Additional details This is recommended method It requires service email to be added to authorized users list for chosen spreadsheet Easy to setup, but
1) readonly
2) requires spreadsheet to be shared or public
Easiest to setup, no need for any credentials, but
1) readonly
2) requires spreadsheet to be shared or public
3) no access to raw/input value
Setup guide read read read read

Create Export/Import task

Go to Export/Import tab, press plus icon, chose Job type to be GoogleSheets and click Add button

Chose GoogleSheets datasource, created above. Set up metas (tables) you wish to update.

Running Export/Import Task

Press Export or Import button to run the task you just created.

[Optionally] After job is finished, open Log tab to see full log of all actions performed. Pay attention to Warning messages (colored red). Every error or unexpected event happened during syncing will be colored red.

Target empty spreadsheet while exporting for the first time. Export job will create necessary sheets/header rows + data for you (more information)

Make sure you have as many physical rows/columns as you need, delete empty rows/columns to boost performance.

Using Google sheets as shared remote database

You can use Google Sheets as remote shared database to be used by several developers (during game development)

Starting with version 1.5.4, we enforce locking mechanism to ensure only one export job is running at a time to avoid possible data collision. We use separate sheet (_dblock_) with one single cell (A1) to hold the lock value. Unfortunately this mechanism is not 100% solid and there is still a tiny chance 2 export jobs run at the same time- in this case you will get a warning message after the export. If you see this warning- review GoogleSheets data to make sure everything is ok and export data one more time if there is any issue.

GoogleSheets API v.4 and Older Unity versions

Since BGDatabase v.1.5 we switched from Google Sheets API v.3 to v.4. If you use Unity 2017-2018, make sure your scripting runtime is set to 4.x. Read more details here