Skip to main content
Announcements
Defect acknowledgement with Nprinting Engine May 2022 SR2, please READ HERE
cancel
Showing results for 
Search instead for 
Did you mean: 
MarcoRaymundoKeyrus
Partner - Contributor III
Partner - Contributor III

How to insert HTML tags in HTML reports by variable

Hi!

I want a generate list like this:

  • Apple
  • Banana
  • Orange

I created a variable to include a message in the body of the email.
SET vList = = Concat (Aggr ('<li>' & MYFIELD & '</li>', MYFIELDAGGR));

In the HTML report, I created the following structure:
<ul> %% vList %% </ul>

In NP 16 it worked perfectly, generating the list, like above.

In NP 19 april, in the output file, the tags <li>;</li>, were converted to &lt;li&lt;/&

Does anyone know how to prevent NP when generating the HTML file to do this conversion?

Labels (2)
12 Replies
MarcoRaymundoKeyrus
Partner - Contributor III
Partner - Contributor III
Author

@Ruggero_Piccoli 

Thank you!
I tested your tip and it worked correctly.
I think it's a good technique to keep HTML code more flexible and easy to understand.

This information is very useful.

Congratulations!

Lech_Miszkiewicz
Partner Ambassador/MVP
Partner Ambassador/MVP

Hi @Ruggero_Piccoli 

i think this should be discussed with R&D as lack of compatibility between v16 and 17+. 
If values of variables, formulas etc are passed on template differently in those versions then any attempt of migration will not be successful. Ehat do you think?

thanks

lech

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.
Ruggero_Piccoli
Support
Support

Hi,

Yes, it could be a problem for a migration, but, maybe, the wrong way of working is the one of QlikView NPrinting 16. I mean if the content of a QlikView variable is placed in the HTML report without any "analysis" it could contain a script that will be executed. So it must be managed carefully.

In any case, the R&D is aware of this behaviour 🙂

Ciao



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.