It is found that for the NPrinting Feb 2021, there is a bug that if the dynamic naming are using the same QlikView variable as the Destination Folder, the folder will not be created.
Environment
QlikView Apr 2020 SR2
NPrinting Feb 2021
Step to reproduce:
1. Set the destination folder like this on NPrinting
d:\%%timestamp_YYYYMM%%\
2. Set the report dynamic naming like this on NPrinting
This issue is solved by Qlik NPrinting May 2021 SR1. From the Release Notes:
In some cases, Qlik variables were not resolved on folder destinations Qlik variables would not resolve when creating folders as destinations, if the same variables were also used in the dynamic naming of the report in the same folder.
Best Regards,
Ruggero
Best Regards, Ruggero --------------------------------------------- When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads with a LIKE if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads with LIKEs if you feel additional info is useful to others.
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.
As alternative, you can evaluate to add the country and city name in the report file name and develop a custom software or script that read the file names and distribute them in subfolders.
If you select the way of creating dummy users remember that you can import them from an Excel file including filters https://help.qlik.com/en-US/nprinting/May2023/Content/NPrinting/DeployingQVNprinting/Import-Users-Fi.... It depends on your scenario but maybe it is faster to import users from a file before every publish task execution. The Excel file with users can be created by Qlik NPrinting from the source app or document.
Best Regards,
Ruggero
Best Regards, Ruggero --------------------------------------------- When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads with a LIKE if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads with LIKEs if you feel additional info is useful to others.
Thanks for sharing, we are aware of the issue. The fix is not included in next version May 2021 and, at the moment, I don't know when it will be released.
Please try to create two different variables with the same content and use one for the folder and one for the file name.
Best Regards,
Ruggero
Best Regards, Ruggero --------------------------------------------- When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads with a LIKE if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads with LIKEs if you feel additional info is useful to others.
This issue is solved by Qlik NPrinting May 2021 SR1. From the Release Notes:
In some cases, Qlik variables were not resolved on folder destinations Qlik variables would not resolve when creating folders as destinations, if the same variables were also used in the dynamic naming of the report in the same folder.
Best Regards,
Ruggero
Best Regards, Ruggero --------------------------------------------- When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads with a LIKE if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads with LIKEs if you feel additional info is useful to others.
This is very different scenario as you are using cycle functionality. With cycle this will not be possible as cycle is creating single zip file as an output therefore destination of that file can only be one (despite the fact that in zip file you actually have reports for combinations of your dimensions).
The only method/workaround for this would could be use of dummy users and user filter (each dummy user would represent value combinations from your cycle)
cheers
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.
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.
As alternative, you can evaluate to add the country and city name in the report file name and develop a custom software or script that read the file names and distribute them in subfolders.
If you select the way of creating dummy users remember that you can import them from an Excel file including filters https://help.qlik.com/en-US/nprinting/May2023/Content/NPrinting/DeployingQVNprinting/Import-Users-Fi.... It depends on your scenario but maybe it is faster to import users from a file before every publish task execution. The Excel file with users can be created by Qlik NPrinting from the source app or document.
Best Regards,
Ruggero
Best Regards, Ruggero --------------------------------------------- When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads with a LIKE if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads with LIKEs if you feel additional info is useful to others.
