Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Tabular Reporting recipients can be re-used in Qlik Cloud using a standard QVD approach with a twist.
This can be helpful if you would like to define a single 'master set' of all recipients and then selectively use some or all of them in different reporting applications.
Some examples:
- Load a subset of recipients for different reporting apps
- Assign different filters to the same recipients for different reporting apps
- Assign different groups to the same recipients for different reporting apps
While QVDs are often used to reload portions of the same data into multiple apps, QVDs also store 'tags' which turns out to be exactly how Qlik Apps reference recipients, filters, and groups.
Lets take a look:
With Qlik Cloud tabular reporting, recipients, groups, and assigned filters can be loaded from any supported data source.
TAGs are used to keep track of which field in the data model represents the recipient, their email address, and optionally, their assigned filter and group.
A minimal sample script could look like this:
The sample script loads a list of recipients, emails, filters and groups as a single table, and then it tags the fields accordingly with predefined tags.
Loading this script 'as is' is enough to create the recipient store in the Qlik app as follows:
as well as the group definitions:
If we decide to store the Recipients table to QVD, as long as the STORE command is issued after the 'tag field' commands as shown below...
it results in a reusable recipient QVD file as follow
that when loaded into a new reporting app...
...will recreate all the recipients, groups, and filters in the new app with NO need to re-tag the recipient, filter, or group tags.
Why is this important? Well first you don't need to retag recipients in multiple places, but second you can unlock the reusability of the recipient file by:
1. Loading a subset of recipients for different reporting apps
2. Assign different filters to the same recipients for different reporting apps
3. Assign different groups to the same recipients for different reporting apps
In this example, a subset of recipients (3 of 6) are loaded into a reporting application by using a JOIN. Use the Email recipient field for the JOIN as it is likely the unique identifier. Note that any LOAD syntax can be applied to load only select recipients (such as KEEP, WHERE etc..)
In addition, this ample also makes new filter assignments and creates and assigns different groups specific to this application.
I hope this helps as a building block to devising a reusable recipient list .
