We have a scenario where we have a large datasource that is currently used to produce a single QVW. What we would like to do is produce a number of smaller QVWs using e.g. Publisher - however, we would like to define the reload schedule and destination folders that these smaller QVWs end up in from an external MySQL table (or config file or similar), rather than through the Publisher GUI. Has anyone done anything similar, or got any recommendations on how to approach this?
Package is executed from the lef to the right starting from “Init Variables” object
First of all we’ve created the following table to store parameters, it can be extended if necessary
Table data:
Variables are used to replace one string with another, for example anywhere in the package where <RootDirectory> is found it will be replaced with C:\Customers.
This script ins increasing variable <loop variable> by one (two times)
This step executes the following SQL to get variables form the databases, before execution <loop variable> is replaced with actual value
This step creates directory if it does not exists
This step copies Dashboard to just created directory, so it is easy to distribute updates
This step is used to create QVD file, if it necessary to create several files we can just add more Export steps or for complex cases we can use transformation object to create QVD files
This step is used to Refresh QlikView dashboard, data is loaded from the same directory where Dashboard is stored
For more technologies supported by our ETL Software see Advanced ETL Processor Versions