If you're using Vizlib Writeback Table, and your app reload time is longer than 2 minutes you might want to try working with binary loads. They can improve speed and performance, which will help you work with your data more effectively.
This is because every time you perform a writeback operation, a reload operation is also required. Binary loads will speed up the reload process, which is where the improvement in performance can be measured.
For an overview of the Binary Load structure please see the Qlik Sense article here.
You can find the full Qlik Sense reference article for binary statements here.
Note on Reload Errors: If you do encounter a Reload Error when using Vizlib Writeback Table, please check our Troubleshooting guide here.
In Qlik Sense, the binary statement loads data from another Qlik Sense app or Qlik View document, and can section access data. It must be placed at the very beginning of the script, and only one binary statement per script is permitted.
The syntax of the statement is
binary [path] filename
- filename - The name of the file, including the extension (.qvw or .qvf)
- path - The file path, which should be a reference to a folder data connection if the file is outside the Qlik Sense working directory.
Binary Load vs. Partial Reload - Comparison
Partial reload can sometimes be used as an alternative for app reloads, as it can match binary load for speed. We've included a short comparison here.
- Initial app load is slower than binary.
- Currently only be supported using the Qlik Engine JSON API, so not all script functions supported.
- Debug requires review of log files, which is more difficult than being triggered from load scripts.
- More complicated setup process than partial reload (please read the Qlik Sense article on structure here).
- Only recommended for app reload times longer than 2 minutes.