Skip to main content
Announcements
Defect acknowledgement with Nprinting Engine May 2022 SR2, please READ HERE
cancel
Showing results for 
Search instead for 
Did you mean: 
mstoler
Partner - Specialist
Partner - Specialist

move on demand to a folder

Hello,

I have an on demand pixel perfect report with a cycle that allows users to pick one or more customers and run the report. The report downloads to a folder.

How can I convert this so that once a month each rep gets a report for each Customer in a directory?  Ideally I would like the pdfs to not be in a compressed folder.

Thank You,

Michael

Labels (1)
1 Solution

Accepted Solutions
Lech_Miszkiewicz
Partner Ambassador/MVP
Partner Ambassador/MVP

Hi @mstoler

one part is basic and simple - you just set distribution to folder and while setting up folder you can make path dynamic based on report recipient attribute and/or Qlik variable - this is all documented in help: https://help.qlik.com/en-US/nprinting/May2022/Content/NPrinting/AdministeringQVNprinting/Folder-dest... 

second part is twisted as currently running cycle in NPrinting will produce zip file and there is no way you can get away from this. You can redesign your approach and resign from using cycle and start distributing reports where your (user/recipient) will be effectively a "Customer" entity with the folder linked to the Rep. So the steps would be:

  • Create NPrinting users using import from excel process - each user is equal with one Customer https://help.qlik.com/en-US/nprinting/May2022/Content/NPrinting/DeployingQVNprinting/Import-Users-Fi... 
    • add their folder attributes - for each customer set the equivalent of REP folder. That means that some customer reports will land in the same folder
    • add all customers to a NPrinting group
    • add that customer filter or its Id as a filter
  • Create publish task
    • add that group as a recipient of your report with the folder destination

For every recipient (Customer) report will be produced and stored to a assigned folder.

That is the way I would do it.

by the way - make sure report name is dynamic and contains at least customer id or name so files won't get overwritten when published to the same folder.

cheers Lech, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful to the problem.

View solution in original post

1 Reply
Lech_Miszkiewicz
Partner Ambassador/MVP
Partner Ambassador/MVP

Hi @mstoler

one part is basic and simple - you just set distribution to folder and while setting up folder you can make path dynamic based on report recipient attribute and/or Qlik variable - this is all documented in help: https://help.qlik.com/en-US/nprinting/May2022/Content/NPrinting/AdministeringQVNprinting/Folder-dest... 

second part is twisted as currently running cycle in NPrinting will produce zip file and there is no way you can get away from this. You can redesign your approach and resign from using cycle and start distributing reports where your (user/recipient) will be effectively a "Customer" entity with the folder linked to the Rep. So the steps would be:

  • Create NPrinting users using import from excel process - each user is equal with one Customer https://help.qlik.com/en-US/nprinting/May2022/Content/NPrinting/DeployingQVNprinting/Import-Users-Fi... 
    • add their folder attributes - for each customer set the equivalent of REP folder. That means that some customer reports will land in the same folder
    • add all customers to a NPrinting group
    • add that customer filter or its Id as a filter
  • Create publish task
    • add that group as a recipient of your report with the folder destination

For every recipient (Customer) report will be produced and stored to a assigned folder.

That is the way I would do it.

by the way - make sure report name is dynamic and contains at least customer id or name so files won't get overwritten when published to the same folder.

cheers Lech, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful to the problem.