• Writeback Settings - Load Script, Audit Columns, Table Settings, Reload

    • Vizlib Writeback Table has a Writeback Settings menu to make changes to your writeback configuration quick and easy to manage.

    This topic contains the following sections:

    Writeback Settings

    Writeback Settings are found in the right property panel, below the Columns menu. In this article we're going to focus on the properties for the Load Script, Audit Columns, Table Settings and Reload sections. If you need further information on the Destination section, you can find a link to the article here. You can also find more information on Writeback Operations in the article here.

    Load Script

    Note: Load Script settings are only displayed for QVD destinations.

    The Load Script settings (Figure 1) allow you to inject (or update) a data load script containing writeback information into the data load script for your app. You need to enter the Data Table Name used to create the input form, then click Inject Load Script (or Update Load Script if a script has already been added). If the script is added, you'll receive a confirmation. If you return an error, you'll receive details about the information you need to correct.

    Figure 1: Load Script

    Audit Columns

    If you would like to build up a record of the changes you make to your writeback table, you can use the Audit Columns 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 drop-down, or use the Qlik Sense expression editor to customise the Timestamp label and User label.

    Figure 2: Audit Columns

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

    Figure 3: Audit Columns 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 drop-down 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

    Reload

    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