Vizlib Home

Vizlib Writeback Table / Vizlib Input Form Guides - Writeback Best Practice

Vizlib Writeback Table and Vizlib Input Form are products with a wide range of features and customization options for your data visualizations. This article gathers together some examples of best practice to help you manage working with them, from installation and setup to managing and customizing table settings. If there's anything you'd like to see added to this article, please visit our feature requests page and start a new topic. 

Note: In this article, Writeback means the instructions can apply to both Vizlib Writeback Table and Vizlib Input Form



The Vizlib Collaboration product suite (which Writeback is part of) has been developed to work across a range of architecture models. If you're not sure what setup would suit you best, you can review the Vizlib Collaboration architecture document here

Back to Contents

Database Backup and Recovery

If you want to use Writeback with a server, you'll need to install Vizlib Server. We've written a guide to working with databases and making sure your installation can be managed efficiently, even if it needs to be backed up or recovered. You can find the database backup and recovery article here.

Back to Contents

Qlik Sense Users

If you're looking for a Writeback solution that operates without a server you'll only be able to use it if you have a Professional Qlik Sense license. When you use writeback with a server, you'll be able to widen access to include Analyzer licenses as well. There's full details in our Features and Plans factsheet here

Back to Contents

Data Load Updates

When you've completed the setup for Vizlib Writeback Table, 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

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.