Just a quick question - Is it possible to import Folder & Subfolder information linked to user properties when using Import Task for Import recipients in NPrinting 17.3.0 (or any other nPrinting 17.X.X)?
I am using Recipient.xls template from Qlik Help page and it does not include those to fields. I tried adding them manualy to the template, import goes through, but fields are not getting updated.
Do you know whether this possible at all?
any help would be apprecaited.
BTW - version 16.X.X and older had that option - i am interested in version 17 and above only.
Solved! Go to Solution.
Thanks for your input. Temporarily this can be a good workaround as well as using QlikView variable.
Regarding my question i guess it remains unanswered as whether Folder and Subfolder Import from XLS is supported.
I guess - so far it is not.
I am going through help documents and it does not say anything about importing Folder and Subfolder information in recipient import from XLS. I just do not know whether this is supported as it used to be in nPrinting 16.X.X?
Your help will be very appreciated - thanks & regards!
Is it supported?? YES or NO? I tried avoiding raising Support ticket for that simple question but i do not have more time waiting for simple answer from Qlik specialists.
I don't think that you can input folder information by import task.
But you can create folder destinations in NP17 and then you define the right folder to a user (recipient) or a group in the publish task.
That is true,
However we have 500 recipients and for each of them we need separate folder.
That being said you have to manually enter folder name for each of them in NPrinting User preview in order to generate folder for each recipient in destination location. If I could use XLS i would just build formula to create folder names based on user names and NPrinting would create folders automatically. Since i cannot import folder "name" for each recipient i have to specify it manually in nPrinting console which is pure waste of time - dont you think?
I think it is possible.
When I tested NP17.3 I have created C:\QlikViewDocs\NprintingReports\\%%User_Name%%\ as a location path and now every user has their reports in the specific named folder.
So instead of entering a folder name for each user, in your case, I would use User_Name and if needed, I would, place a Qlik variable in the location path. Just keep in mind that you can use name of the user already and do not need to use Qlik variable for it.
When defining a location you can use:
Thanks for your post. I'm sorry to see that you were not able to get a response as quickly as you wanted. Please keep in mind that participation in the community is voluntary, and that it may take some time for members or employees to reply to a post. When an urgent issue arises, please create a support ticket to ensure that you receive a response in the desired time frame.
Feel free to let me know if you have any questions about the community.
Qlik Community Team
I will test it next week - but i agree - that would be a nice workaround. I have never thought about using %%tags%% in places like destination path so it really may serve my purpuse. Maybe it is not an answer to my question, but definitely would solve my issue.
Let me get back to you bit later after testing it - but in general... Yeah-great TIP - THANK YOU!
Hi Jeremy - no worries. I understand, that community participation is voluntary and i very appreciate everyones contribution.
I had to reply to my own post as it disapears from the list of topics after couple days in "iddle: mode" when nobody is discussing it, so eventually nobody would answer it anyway. The best example of that happening is this post where i stayed quiet an nobody answered/followed discussion and I understand that sometimes these are difficult topics like (GeoAggrGeometry() - JSON protocol parse error ), and sometimes it is just a simple Yes or No (like this nPrinting post), and as it is not clearly stated in Qlik Help documentation neither way i have asked qlik experts / product supporters hoping for a quick answer.
Despite the fact that there is no clear answer to the post question, Alex has taken a challenge and proposed very interesting solution which i am very greatful for.
Do not get me wrong Jeremy, I was not demanding and like i said i very appreciate everyones inputs, contribution and time spent on helping others.