Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi Guys,
I know some people asked for this question long time ago, but I still don't see a positive answer. We are currently working on Feb 2020 NP 19 version. While sending email to users, most of our users will receive multiple cycling reports. Seems all reports are in a .zip file as attachment by default, and our users really don't like it. Also dynamic naming is on individual report, the .zip folder name is default to cycled field name with some variables and we don't want to show the cycled field name to users. If we have to keep the .zip how to name .zip folder?
Thanks in advance.
Fion
Hi,
I understand limitations of such solution and I dont want to argue them, but as a workaround it may do the job just as you wish.
Hi,
I understand limitations of such solution and I dont want to argue them, but as a workaround it may do the job just as you wish.
Hi Lech,
Thanks so much for your feedback. I think your workaround can be used in our app as well, at least the .zip folder name will not look that weird.
Hi Lech, i found your answer of 2020 to Fionnas question. We have now moved 4 years: did anything change/ improve?
I have the same request:
Seems all reports are in a .zip file as attachment by default, and our users really don't like it.
Now NPrinting is sending 1 email attaching 1 zipfile containing multiple pdfs based on 3 Cycled fields.
I would like to send:
1 email attaching multiple pdfs based on 3 Cycled fields.
or
multiple emails attaching 1 pdf based on 3 Cycled fields.
Is this possible yet?
Thank you in advance,
Johan
HI @JohanL74
No, nothing has changed since on that matter and given current status in NPrinting development it will not change!
Sorry.
Regarding workarounds depending on the data there may be a way. If the number of cycle values is not large you potentially could use those values to create "dummy users" and use those users with respective filters to produce report for each value of the cycle with reports being sent to alternative emails attached to those dummy users.
I personally use this approach on few projects and it works ok as long as you spend enough time designing end-to-end solution which fully automates the process.
cheers