How do I stop LiveReport HTML encoding my results

cameronl@hayesis.com.au

In LiveReports (and/or LiveReports Extensions) how do I stop it from encoding a valid custom URL returm value to a string ?

eg the LiveReport SQL generates the following result field:
<A HREF="http://dm-test/otcs/llisapi.dll?func=ll&objaction=overview&objid=10887595">New Document.doc</A>

I would like it to write to the page as:

<TD ALIGN="LEFT" NOWRAP>; <A HREF="http://dm-test/otcs/llisapi.dll?func=ll&objaction=overview&objid=10887595">New Document.doc</A> </TD>

But LiveReport HTML encodes it to:
<TD ALIGN="LEFT" NOWRAP>; <A HREF="http://dm-test/otcs/llisapi.dll?func=ll&objaction=overview&objid=10887595">New Document.doc</A> </TD>

Find more posts tagged with

Comments

Colin_Schmidt

Have you tried using the “CHR(38)” (or whatever ASCII code) for the various special characters?

Colin J. Schmidt

From: eLink Entry: Content Server LiveReports Forum [mailto:livereportsdiscussion@elinkkc.opentext.com]
Sent: Thursday, June 01, 2017 5:02 PM
To: eLink Recipient <devnull@elinkkc.opentext.com>
Subject: How do I stop LiveReport HTML encoding my results

How do I stop LiveReport HTML encoding my results

Posted by Lyon, Cameron On 06/01/2017 04:54 PM

In LiveReports (and/or LiveReports Extensions) how do I stop it from encoding a valid custom URL returm value to a string ?

eg the LiveReport SQL generates the following result field:
<A HREF="http://dm-test/otcs/llisapi.dll?func=ll&objaction=overview&objid=10887595">New Document.doc</A>

I would like it to write to the page as:

<TDALIGN="LEFT" NOWRAP>; <A HREF="http://dm-test/otcs/llisapi.dll?func=ll&objaction=overview&objid=10887595">New Document.doc</A> </TD>

But LiveReport HTML encodes it to:
<TD ALIGN="LEFT" NOWRAP>; <A HREF="http://dm-test/otcs/llisapi.dll?func=ll&objaction=overview&objid=10887595">New Document.doc</A> </TD>

[To post a comment, use the normal reply function]
Forum:	Content Server LiveReports Forum
Content Server:	Knowledge Center CS16

The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.

cameronl@hayesis.com.au

Using the character identifier codes in the SQL doesnt seem to help as that parsing out of the special characters happens after that, I think as the page is built.

CHAR(60) still gets encoded to <
CHAR(62) still becomes >

CHAR(34) becomes "

CHAR(38) becomes &

Greg Griffiths

Cameron,

I suspect you will need to amend the WebLingo or perhaps use WebReport.to present the UI layer.