Vizlib Home Try Vizlib

Vizlib Writeback Table Guides - Integration Setup - Google BigQuery

If you're using Vizlib Writeback Table with Vizlib Server, you'll need to set up and select an Integration to store your data and any changes you make. Integrations allow you to connect Vizlib products with your existing solutions (e.g. an email server or a database) to improve data sharing and collaboration. Integrations are configured in the Vizlib Management Console (VMC). 

Vizlib Writeback Table can integrate with different data output types, and we're going to use Google BigQuery in this example. You can find a full list of supported products here 



Note on Authentication: Google BigQuery integrations currently only use Service Authentication   with Vizlib Writeback Table

Note on Supported ColumnsStruct, array and bytes column types are not currently supported. 

Before you Start - Checklist 

Before you add an integration, make sure you have all the information and permissions you need. Work through all the items in this list and then you'll be ready. 

  • Installations - Vizlib Writeback Table and Vizlib Server should be installed before you start. We have online tutorials for installing Vizlib Server and Vizlib Extensions to help you (Vizlib Products are all installed in the same way, so while the tutorial uses Vizlib Library, it can also be used for Vizlib Writeback Table). 

Note: If you haven't installed any Vizlib products before, please install the product (Vizlib Writeback Table) then install Vizlib Server. If you have already installed Vizlib Server, please perform a restart after installing Vizlib Writeback Table.

  • VMC login / Password - to create and configure the integration, writeback destination and check the audit trail. The VMC is installed as part of Vizlib Server
  • Qlik Sense Connection - your Qlik Sense environment needs a data connection to select and load data from a Google BigQuery database. You can find full setup instructions here
  • Authentication - remember only Service Authentication can be used. 
  • Column Types - remember columns with type struct, array and bytes are not supported. 
  • Project ID / Key File - Google BigQuery configuration values used to set up the integration. The ID and file are found in your service account in the Google Cloud Console, please see more information here
  • Dataset / Table Name - to configure the destination type. 
  • App Name - the app you want to connect to the destination type. 
  • Writeback Operation and Reload Option - to configure Writeback settings for the destination.
  • Security Rule - to set up secure access for a destination, a security rule should be configured in the VMC. See our security rules article here for more information. 

Back to Contents

Adding an Integration

The first step to connecting is to add or configure an integration.

  • Log in to the VMC. You should see the dashboard, with all your current integrations listed in the top left panel (Figure 1). The symbol indicates a successful setup, and  indicates a setup error.

Figure 1: VMC Dashboard Integrations, with integrations highlighted. 

  • Go to System Settings, and click Integrations to open the Integrations homepage (Figure 2). Integrations with errors are indicated by .

Figure 2: Integrations Page

  • Click Add Integration to open the pop-up screen (Figure 3). 
  • Select bigQuery as the Type, and pick a unique Id. This will be displayed in Vizlib Writeback Table so keep that in mind when you're creating it, we've used bigQuery-test here. 
  • Set the integration to Public (available for every user with VMC access) or Private (access only for the creator, and users with Admin and Root Admin permissions). 
  • Enter the Google BigQuery Project Id
  • Click the button at the far right of Upload Key File to open the explorer and locate the Key File. When the upload is complete, the file name (or path) is displayed and the Add Integration button turns blue (enabled). 

Note on Key File: Adding a Key File does not affect the settings of any other Google BigQuery integrations (e.g. in contrast to Oracle Wallet files) and the Key File can be referenced in more than one integration on the same server.  

  • Enter a Proxy value if you require one (this is an optional field). 

Figure 3: Integration Fields

Figure 4: Add Integration

  • Click on Add Integration when you're finished. You should see the new integration listed in the dashboard. 

Check on Integration Status and Errors: Your integration should display on the dashboard with a green tick icon before going to the next step (Figure 5). If it's showing an error, follow the advice in the message (e.g. an incorrect port number has been entered).

Figure 5: Integration Completed Successfully

Back to Contents

Adding a Destination

Now, you'll need to add a Destination, which is the data source for your Writeback table. 

Note on LockingBy default, an auto-lock is triggered when a writeback operation is performed on a destination, and stays in place until the operation completes. You can enable the Allow Locking setting in Access and Security if you'd like to extend the locking function  

  • In the VMC menu, click on Writeback Settings, then Destinations and Security. You should see the list of current destinations displayed on the page (Figure 6). 

Figure 6: Destinations & Security

  • Click Add Destination and you'll create a new entry. Click on the destination ID to add your destination data (Figure 7 and 8). Your destination will already have an ID and configuration generated from the last entry in the table, but you'll be able to change this in the next step.

Figure 7: Destination Fields

Figure 8: Destination Settings

  • Enter a  destination id, then go to the Writeback Settings panel and select BigQuery as the Destination Type

Check on Destination ID: Destination ID has to be a unique value, or you won't be allowed to save your changes. 

Now you can start to configure your destination. The Writeback Settings panel (Figure 9) holds information about the level of functionality allowed in your Vizlib Writeback Table app. 

Figure 9: Writeback Settings

  • Select the destination you need from Destination Type.
  • Select the writeback Operation (Insert, Update, and Delete). For more information on Writeback operations please see our article here
  • Choose one of the Reload Options (No Reload, Reload App, Partial Reload App, Reload Task)

Check on Reload Options: Reloading the app means when data is written back to the destination it is immediately available to other users, so you'll probably have to pick an option which enables reload. You can find more information in our article here. Reload Task is set in the Qlik Management Console, you can find more information here

  • Add the writeback App you want to use. Apps are listed alphabetically with the App ID displayed. The app id is intended to make it easier for you to find an app you need to use, or one you've used before. 

In the Destination Settings panel (Figure 10) enter information about your data source.  

Figure 10: Destination Settings

  • Select the integration from Pick DB Integration
  • Select the database schema from Dataset
  • Enter the Table Name which will store your writeback data. 
  • Enable Allow table creation if you want users to create a table and copy it to the database. 

Note on Allow Table Creation: Creating tables could change and disrupt the data model, so you should only activate this option if you really need it. 

  • Enable Allow columns creation if you want users create a column and copy it to the database. Any empty cells will be passed with a null value. 

If you need to lock the data structure that's sent from your writeback table to your destination, you can do this in Fields Validation (Figure 11).

Figure 11: Fields Validation

Note on Field Names: Writeback operations using this destination must contain exactly the same field names as defined here.

  • Slide the toggle right to enable the setting, and click on Add Field to create a new entry. 
  • Add the Field Name used for updating the table. 

Check: The field name must match the writeback operation field name, or you'll return an error. 

  • Enable Allow Null if you want to pass null values to the table.

Vizlib Writeback Table has a default auto-lock function which is activated when a writeback operation is triggered. You can also use the Locking settings (Figure 12) to extend the locking function for the destination. If you enable Allow manual locking, the destination will lock when you start to input data, and unlock the table when you have finished  When locking is enabled, an icon appears in Vizlib Writeback Table.

Figure 12: Locking

  • Select Allow manual locking, then choose between Lock only the current destination, or Use Lock Group. You can find out more information on lock groups here
  • If you're using Insert as the writeback operation, you'll also be able to select Queue, which means updates will be "queued" and completed before the data is re-loaded. This option is helpful for managing updates from multiple users for a single destination. You can find out more information on queued writeback here.

If you need to restrict which users can work with the destination, you can do this with Access & Security settings (Figure 13).

Figure 13: Access & Security

  • Check Secure Destination to enable secure access if you need it. 

NoteThis setting is configured with a security rule to allow access to the destination, so users won't be granted access automatically if Secure Destination is enabled. You can find out more about security rules in our article here 

  • You can choose to make the destination Public if you want other Content Admin users to be able to re-use it, or Private if you want to limit re-use to the creator (you), Admin and Root Admin users
  • Enable Audit trail if you want to create an audit trail for the destination.

Note: You can access audit trails on the Writeback Audit page of the VMC, there are instructions on working with audit trails here, and you can also watch a step-by-step video tutorial on setting up an audit trail here.

  • Click Add Destination to save your destination in the VMC. 

Back to Contents

Adding Writeback Settings


Now, you need to go to Vizlib Writeback Table and configure your app to write back to the destination. You'll find these settings in the property panel under Destinations. 

  • Open your Qlik Sense Hub and find the Vizlib Writeback Table sheet you'd like to work with.
  • Open the sheet in Edit mode, then go to Destinations in the property panel. 
  • Click on Vizlib Server in Pick Destination (Figure 14). 

Figure 14: Pick Destination

  • Select a Writeback Destination from the dropdown (Figure 15). This is where your data will be saved.  Google BigQuery destination paths follow the structure 
Destination|Database Type|Table Name

An example path for a destination would be  


Figure 15: Destination Path 

  • Click Done to save the changes to the sheet. 
  • When you've completed the changes and saved them, you'll be able to write back to the destination you've configured.  

Back to Contents

Working with Vizlib Writeback Table - Data Load Updates

When you've completed the setup, you will need to update your data load script to make sure data is loaded correctly back into the app. Otherwise it will look like the operation isn't completing. 

The data load script is part of the Qlik Sense environment, you can find out more about editing the data load script in a Qlik Sense app here

Tip: Use * to specify all columns in the table should be loaded. This is especially useful when you expect the content of the table to change (e.g. by adding new columns). 

When you complete these steps, the table will be loaded back into the app correctly and you can start to use Vizlib Writeback Table to help make the most of your analytics solution.   

Back to Contents

Vizlib is the author of this solution article.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.