Connect to BigQuery Data Using the Script Function in Claris FileMaker Pro

Claris FileMaker is a low-code database application development tool that enables users to create custom apps for managing and organizing data. It combines a powerful relational database engine with an intuitive interface, allowing both technical and non-technical users to design and deploy applications across desktop, web, and mobile platforms.

In this article, we'll explore how to use the CData ODBC Driver for Google BigQuery and FileMaker scripting to connect to BigQuery data.

Getting Started

---

Create an ODBC Data Source for BigQuery

If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.

Google uses the OAuth authentication standard. To access Google APIs on behalf of individual users, you can use the embedded credentials or you can register your own OAuth app.

OAuth also enables you to use a service account to connect on behalf of users in a Google Apps domain. To authenticate with a service account, register an application to obtain the OAuth JWT values.

In addition to the OAuth values, specify the DatasetId and ProjectId. See the "Getting Started" chapter of the help documentation for a guide to using OAuth.

When you configure the DSN, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing reports and visualizations.

Connect and Sync BigQuery data with FileMaker Using Scripts

In this section, we walk through the steps to connect live BigQuery data to FileMaker using the CData ODBC Driver for Google BigQuery and the Script function. During the initial import, FileMaker brings in all data from the external data source. From the second import onward, it updates only the data that has changed in the external source (a differential update). You can also replace the data in the current record order and schedule these differential updates for automated syncing.

You can download and install the latest version of FileMaker Pro for your Mac/Windows/Linux systems from this link.

Connect and sync BigQuery data with FileMaker using scripts

Scripting in FileMaker automates complex tasks and workflows by running a sequence of actions with a single command. By using scripting to integrate with BigQuery, you can automatically connect to, import, update, and replace BigQuery data within your FileMaker applications, streamlining data management and improving efficiency.

First-time importing and adding BigQuery data using script

In this section, we'll use scripts to import BigQuery data into FileMaker by following these steps:

1. Open FileMaker Pro. Navigate to Create from the left panel and select Blank > Create.
👁 Create a new application in FileMaker

2. Enter a filename of your choice and click Save.
3. In the Manage Database window, go to the Tables tab and create or rename the table where you want to display the BigQuery data.
👁 Create or rename existing the table

4. In the Fields tab, create and add the fields you want to use in the table.
👁 Add the necessary fields.

5. In the Relationships tab, add table relationships if there are multiple tables, then click OK.
👁 Add the table relationships.

6. To reopen and modify the table structure, go to File > Manage > Database.
7. Navigate to Scripts > Script Workspace.
👁 Open the Script Workspace.

8. Select New Script to open a new script workspace.
9. From the Steps panel on the right, select Records > Import Records > Insert into Script.
👁 Insert into script from import records.

10. In the Specify Data Source dropdown, choose ODBC Data. 👁 Click ODBC Data from Specify data source.
    
11. Select CData GoogleBigQuery Sys from the Select ODBC Data Source window, and click Continue. Enter your BigQuery credentials and click OK.
👁 Select the data source driver.
👁 Enter the data source credentials to aunthenticate.

12. In the Specify ODBC SQL Query dialog, enter the SQL query in the SQL text editor to import the desired BigQuery data.
👁 Specify the SQL query.

13. Alternatively, select Query Builder to open the SQL Query Builder window. Choose the target table from the Tables section and relevant columns from the Columns section. Click Insert into SQL Query after each selection to auto-generate the query. You can also manually edit the query using WHERE and ORDER BY clauses or the designated tabs. Click OK to finalize the query.
👁 Specify the columns in the table to auto-generate the SQL Query.

14. Click OK.
15. In the Specify import order option, click Specify and enter the BigQuery credentials.
👁 Click Specify.

16. In the Specify Import Order window, define the import order for the target fields you added earlier. Select Add between the source and target fields to insert the BigQuery data as new records in the table. Click Import.
👁 Select

17. The script now appears in the workspace. Click Run to execute the script and process the import.
👁 Click Run to execute the script.

18. FileMaker imports the BigQuery data as a table.
👁 The BigQuery data gets loaded.

Update or Replace Imported BigQuery data Using a Script

After importing the BigQuery data into FileMaker, use scripts to update or replace any changes made in BigQuery by following this process:

1. Go back to the Script Workspace by following the steps mentioned in the earlier section.
2. Select the existing script, click the settings button, choose Specify under Specify Import Order, and re-enter the BigQuery credentials to authenticate.
👁 Click Specify again from the previous script.

3. In the Specify Import Order window, choose Update between source and target to update the imported BigQuery data. This updates the target's found set with BigQuery data values from selected fields when the match fields have the same values. You must define at least one match field in the mapping and select the checkbox Add remaining data as new records. Click Import.
👁 Select
👁 Match at least one field in the mappings.

4. Alternatively, choose the Replace option instead of Update, based on your use case. This replaces the selected fields in the target's found set with BigQuery data in the current record order. Click Import.
👁 Select

5. FileMaker adds the script to the workspace. Click Run to execute the script and process the import query.
6. FileMaker imports the updated or replaced BigQuery data as a table.

Get Started Today

Download a free 30-day trial of CData ODBC Driver for Google BigQuery to integrate BigQuery data into Claris FileMaker and work with BigQuery data in your FileMaker applications.

Reach out to our Support Team if you have any questions.