Vizlib Home

Vizlib Writeback Table Settings - Audit Trail, Table Settings, Reload

Vizlib Writeback Table Settings

Vizlib Writeback Table has a Writeback Settings menu to make changes to your writeback configuration quick and easy to manage. These settings are found in the right hand panel of the Writeback Table Editor (Figure 1), below the Columns menu.

Figure 1: Writeback Settings

There are 4 sections for Writeback settings.

  • Destination contains configuration settings for writeback data output and writeback operations.
  • Audit Trail contains settings to enable and customise an audit trail.
  • Table Settings manages the formatting of the output table.
  • Reload settings configure when writeback operations are performed. 

In this article we're going to focus on the properties for the Audit Trail, Table Settings and Reload sections. If you need further information on the Destination section, you can find a link to the article here

Audit Trail 

If you would like to build up a record of the changes you make to your writeback table, you can use the Audit Trail section to set this up. There is a Standard audit trail set as the default (Figure 2), or you can choose None to disable the function completely. 

You can select the Timestamp format which you'd like to use from the dropdown, or use the Qlik Sense expression editor to customise the Timestamp label and User label

Figure 2: Audit Trail

You can choose to customise the Timestamp format of your audit trail, by selecting the Custom option from the dropdown. The Timestamp custom format will be displayed, and you can use the Qlik Sense expression editor to enter the format you need. (Figure 2).

Figure 3: Audit Trail Custom

Table Settings

The Table Settings section (Figure 4) lets you set the Page size for the table and the number of rows it should display. 

You can also choose display a row number in your tale by enabling Show row number. If you need to change the row number label you can enter any changes in the text field. 

The Show Warning when this action is required dropdown adds a check to any actions requiring a full and/or locked data set. This setting is applied by clicking the Lock icon next to the Writeback data button in your table. 

  • No warning - No dialog shown.
  • Full data set - Show a dialog for full data set. 

You can select the Fetch all rows setting if you need all data in the table to be loaded, rather than a subset of rows. 

Figure 4: Table Settings

The Allowed Row Actions setting controls permissions for deleting, adding or duplicating rows (Figure 5). If a 0 is added in the expression text box, the permission is granted, so in this example adding rows is permitted, but deleting or duplicating rows is not. 

Figure 5: Allowed Row Actions

You can check these settings by right-clicking on the writeback table in Analysis mode (i.e. closed for editing). This will display the list of available row actions. Figure 6 shows an example where add, delete and duplicate are all permitted. 

Figure 6: Allowed Actions List


The Reload section (Figure 7) contains settings relating to when a reload action is performed on the writeback table. You can choose from 

  • No reload - No reload when writeback is called. 
  • Reload app (default) - The app is reloaded when writeback is called, overwriting any existing data. A potential use case would be before generating the latest version of a report. 
  • Partial App Reload - The app is partially reloaded when writeback is called, so new values are added without overwriting any existing values. A potential use case would be for refreshing or reloading data in dashboards. If you'd like to learn more about partial reload functionality, please see the article here

Figure 7: Reload

Related Articles

You can find a list of related articles in the Vizlib Writeback Table Overview  

Writeback Operations - You can find more information on Writeback Operations in the article here  

Kenneth 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.