NPrinting - allow for other templates (XLS,etc..) HTML output to be embedded in email body
NPrinting 16 allows to create template for example in Excel, then set the output format in publish task to HTML and use that output as embedded content in email body.
NPrinting 17+ allows only for HTML reports (based only on HTML templates) to be embedded).
This is quite a big feature gap - and it is hidden trap 🙂 , as it is not listed on feature gap list.
As many customers built their reports using XLS templates (as they are much simpler to build, design, format, conditional format cells etc) and used the HTML output of those in email content. Workaround is obviously to rewrite those reports to HTML, but it is a lot of work. Customers where such solution was used will not be able to migrate easily.
Indicating if that feature will be available back again in NPrinting will help us decide which direction we will take furter development with some of our clients.
Thanks!
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.
Thanks for the suggestion. Please note that sometimes the HTML generated from Microsoft Office templates is not standard and can generate rendering issues also in email bodies. So My suggestion is to use HTML template to have a better control of the resulting code.
I agree with you and understand limitations and consequences of using such approach.
I have posted this idea based on the fact that we were able to do this in NP 16 and now we need to evaluate if it is worth re-writing reports written this way to pure HTML template.. or if we should just wait some time for the feature so then we can just simply migrate.
This is also a major feature gap for our organistation (large bank). All of our existing v16 solutions make use of the Excel embedding functionaility mainly because of the flexibility of using Excel as well as for financial reporting etc
Only after migrating our solutions to v20 (June 2020) were we made aware that this feature was no longer supported. It was not noted in any release documentation and even Qlik support confirmed that it WAS supported, but then back-tracked a few weeks later saying it was not.
Please consider adding this functionality to a later release.
