EvaluateRelevance() only returning 4KB of data

Reporting
1

(imported topic written by jnmoore91)

Hey All,

So I recently switched from 7.1 to 7.2 and I notice that EvaluateRelevance (when returning one string of data) is now limited to 4KB of data. Is this a bug or is this intentional? B/c it’s hard to build my tables with a limit length of 4096 :frowning:

–Jerroyd

2

(imported comment written by jnmoore91)

Re-create situation with:

<script> var temp = EvaluateRelevance(
"concatenation of names of bes fixlets"); document.write(
"length: "+temp.length+
"<br>"); document.write(temp); </script>

edit:

Actually I found this is browser dependent. FF limits the node length to 4096, however, IE doesn’t, however, in 7.1 I did not get this problem :frowning:

3

(imported comment written by Lee Wei)

I did a quick test for you on my system.

I have Web Reports 7.2.1.357.

On both FireFox 3.0.12 and IE8, I get “length: 1391131”

4

(imported comment written by jnmoore91)

Hi Lee,

I’m using Web Reports 7.2.4.60

on FF 3.5.1

Using the script above on a blank report returns a partial list of the bes fixlets truncated to length 4096.

I don’t know if it’s a FF thing or a Web Reports thing, but my FF users won’t be able to use BES Web Reports :frowning:

5

(imported comment written by Lee Wei)

I duplicated the problem as you have indicated.

The problem seems to be combination of FireFox and Web Reports 7.2.4.60.

FireFox with Web Reports 7.2.1.357 is OK,

Web Reports 7.2.4.60 with IE is OK.

I will file a report about the issue.

Reference# for report: 27790

Lee Wei

6

(imported comment written by MikeOttum)

Hi Jerroyd,

Good find on this bug. The reason that it used to work in 7.2.1 and does not work in 7.2.4 is that we changed the implementation of EvaluateRelevance() in order to optimize performance for large result sets. It used to use Node.textContent (which works for all lengths, but is slow) and now uses Node.nodeValue (which has the 4096 character limitation in Firefox, but is fast).

Luckily, there is a workaround that is both fast and correct in both IE and Firefox. I have the workaround implemented and am going to post it to the forum soon. It will involve replacing the wwwroot/JavaScript/EvaluateString.js file on your Web Reports Server box. We may also release a Fixlet to address this more broadly. In addition, this bug (#27790) will be fixed in the next release of Web Reports.

Thanks for finding this for us, and I apologize for the bug.

Mike

7

(imported comment written by MikeOttum)

The updated EvaluateString.js file is available for

download

. Please replace

BigFixInstallDir

\BES Server\BESReportsServer\wwwroot\JavaScript\EvaluateString.js with this new file. You do not need to restart anything. If you have any problems, please post to this thread.

8

(imported comment written by MikeOttum)

Note that you may also have to do a hard refresh (ctrl-r) on the page in order for your browser to bypass the old script in your cache.

9

(imported comment written by jnmoore91)

Terrific. I all for a performance increase, especially if it my scripts benefit from it! Thanks for the patched JS file.