Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello, do I understand correctly that NPrinting can't create dynamic subfolders based on a variable containing the same values as a cycled field, as explained in the thread below?
Hi,
Sorry to say but yes - this is not possible.
cheers
Hi,
Sorry to say but yes - this is not possible.
cheers
Hi,
In Qlik NPrinting May 2021 SR3 there is this issue solved:
Qlik variables used in folder destinations were not working correctly
Qlik variables used to define folder destinations were not replaced with their values when used on publish tasks with multiple users or in reports with dynamic naming.
So it should work in the version you installed.
Best Regards,
Ruggero
Does this apply to scenario where variable is dependant on the field used in report cycle? That would mean that for every combination of fields used in cycles we now can create separate folder?
thanks
Lech
For the scenario where field used in cycles is also used in variable folder this is still not working. I just tested it on May 2021 SR3 version
I have a Qlik Sense app created with regular Ctrl+0+0 test script. I created table 1 object for the report and i created variable:
In NPrinting:
I did the same tests ages ago and nothing seems to change since. My conclusion is that variable folder name cannot go to the level of fields used in cycle. So i stand by my answer to the original question I say that this is still not possible.
Would you be able to comment on this? Also @Frank_S - I saw you have accepted Ruggero's solution so I assume it also works for you - could you please provide information as where in the above scenario I made a mistake that i did not get all 4 folders created?
thanks
Lech
Hi @Lech_Miszkiewicz ,
You are right. The bugfix I posted was related to file names in case of cycles, so sorry it was my mistake.
I did tests also in May 2021 SR4 and variables used in destination folders are evaluated only one time for each publish task execution. It doesn't matter if one report with cycle is included in the publish task. The usage scenario is, for example, use a variable with today date as text to deliver all generated reports on a single folder daily. You schedule the publish task every day, the variable is evaluated one time with today date and used to create a single folder.
Instead add a variable, for example, made with the formula GetCurrentSelections(Year) and inserting a report cycled by the field year will result in a single destination folder with all cycled reports inside.
I hope I have to clarify and sorry again for my misunderstood.
Best Regarsd,
Ruggero
Thanks for all of this good information. I followed advice in another thread to create dummy NPrinting users, one for each folder that I want, and then made the user variable part of the report destination.
I also put the dummy users into an NPrinting Group and made that Group a recipient of the Publish Task. That way they are easy to manage over time.
(The only problem with this method: Each dummy user must have a unique email address. It's not hard to make up fake emails, but there's a risk that some day one of those emails becomes real somewhere in the world.)
🙂 Thanks @Ruggero_Piccoli
All good - I thought I was doing something wrong. At the same time I hoped you were right and that we would now have ability to create folders based on cycles.
Anyway it is what it is - Ciao!
Hi @Lauri
It is slight chance that one of those emails becomes real. You can probably pick some random domain like
123@fghjkl.xyz - so some random characters. It is very unlikely this email address will be created. Otherwise all steps you have taken as far as I know are the only possible way at the moment
cheers
L