I would like to schedule a report to be sent on a daily basis to different users filtered by department. I have created the filters already. Do I need just one publish task or multiple publish tasks according to the different users?
It is a very tricky question and I need to be careful how I answer it.
I can at least see 3 solutions:
Pros and cons of each solution:
Pros - easy to build and maintain, transparent and self explanatory
Cons - depending on number of users this task may take a lot more time to run as it needs to generate report for each user separately (despite the fact that some users belong to the same group)
Pros - easy to build, transparent and self explanatory, depending on number of users this task may take a lot less time to run as it needs to generate only one report for each department
Cons - you have to create multiple tasks.. If there is new department in your data it will need to be added manually as new task
Pros - Data driven solution does not require much NPrinting maintenance and depending on number of users this task may take a lot less time to run as it needs to generate only one report for each department
Cons - Works only as email distribution (not folder/news stand/hub). Requires additional changes to Qlik application as logic sits there, requires dummy users (not all companies like to take that approach), requires good understanding how whole process will work
My choice would purely depend on generation time of that report. I would start from Solution 1..., I also used to use solution 2 in the past, but only because solution 3 was introduced lately and was not present earlier....Right now I would only consider 1 and 3.
hope this helps
Thank you for the detailed response. I need to add that these reports are to be sent through email on a daily basis. For now, the users are not to be granted access to he newsStand. Does this have an effect on any of the responses above?
Well if email is the only distribution then all 3 options are ok and can be considered. An as I said before I would choose between option 1 and 3 purely based on time required to produce all those reports (which only you can test and decide).
@Pomna is each department getting the same report distributed differently or a individual report for each dept?
Example same report: Report---- Dept A, Dept B, Dept C. Has all data for all departments
Example different reports:
Filtered Data Report for ---- Dept A
Filtered Data Report for ---- Dept B
Filtered Data Report for ---- Dept C
@Lech_Miszkiewicz To the original question, if you are going route two in my example, you would have to set up different task for each department correct? The dummy filter just allows you to filter the task/report and variable email to whom it is going to?
Route 2 - correct, this option sets up task for each department. There is no dummy filter in it (or at least I did not mention it in scenario 2) as it is not required at all. I did mention it in scenario 3 which has variable recipients and dummy recipients with linked department filter. Since you are referring to scenario 2, you are setting up individual filter for each department (not dummy) and you dont need to use variable recipients. We are assuming that those recipients will always receive report for department this task is sending report to, hence they can simply belong to a group representing this department.
@Lech_Miszkiewicz Thank you for clarifying!
@Pomna I wanted to be sure there was not a new way of doing this. I currently run Sales data 7 times a day and divide it by reporting structure. Filtered at the top level of reporting. Similar to your department set up. Must make sure you have associated fields with a common dimension or set up as Lech stated above. Then I did create 7 different task to run these with triggers throughout the day. We did set up email aliases that send to one email and blast out from there, as there was no email variable when we originally set this up. Great fix now with the email variable.
One last thing to note is that if you have a large report or a report with any type of leveling or page cycles it can slow things down when running multiple departments. I have found best practice is to run the report triggers from smallest to largest with some slight staggering between trigger times. This keeps the engine from bogging down with all sorts of levels and page cycles happening simultaneously. Hope this helps!
Its the same report filtered by department. Each department gets only data that concerns their department. For example customer satisfaction rating by department. Each department head gets only ratings for his department on a daily basis.