Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in Toronto Sept 9th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
rwunderlich
Partner Ambassador/MVP
Partner Ambassador/MVP

New version, 1.11, of DocumentAnalyzer

I've posted a new version  of DocumentAnalyzer to http://robwunderlich.com/downloads/. Changes for this version 1.11:

- Now correctly analyzing Fieldnames that contain special characters.

- Fixed bug where fields where not being detected in macros.

DocumentAnalyzer is a QVW that will analyze what fields are actually be used in another QVW.

-Rob

http://robwunderlich.com

9 Replies
Anonymous
Not applicable

Hi Rob

Your document analyzer looks fantastic, however i keep getting the following error when i'm trying to use it.

Any ideas??

Cheers

OutOfMemory.bmp

rwunderlich
Partner Ambassador/MVP
Partner Ambassador/MVP
Author

Based on the log you posted, your document appears to have many objects. It's likely I haven't tried DocAnalyzer against something with that many objects and there is a memory issue I need to address.

Can you try DocAnalyzer against a smaller doc, just to make sure it works for you? If it does then I can go about looking at the memory issue.

-Rob

Anonymous
Not applicable

Hi Rob

Yes the document i am trying to analyze does have many objects. I have tried it on a smaller document and it works perfectly.

Brilliant work by the way.

Robbie

Not applicable

Hi Rob,

I thought you might be interested to know that your DocumentAnalyzer brought to light something interesting about the way QlikView is encoding values in the XML content of QVW files. 

Your statement:

   LET delimChar = chr(01);

in the 'Script Variables' section of the load script produces the following XML element to be written to the qvw's <DocumentSummary> section:

<VariableDescription>

  <Name>delimChar</Name>

  <IsConfig>false</IsConfig>

  <IsReserved>false</IsReserved>

  <ShownValue></ShownValue>

  <RawValue>SOH</RawValue>

  <Comment></Comment>

</VariableDescription>

The SOH character (or binary 1 byte) is not valid XML so any XML parser parsing this content will treat it as a syntax error.  I suppose QlikView should base64-encode the content of the <RawValue> element or provide an alternate <BinaryRawValue> element for variable values that contain invalid XML content.

rwunderlich
Partner Ambassador/MVP
Partner Ambassador/MVP
Author

Interesting to know.

By the way, someone reported the DocAnalyzer was skipping objects that exsited only in Containers She sent me a fix but I haven't had a chance to get it uploaded yet. Shouold get to it this weekend.

-Rob

Not applicable

Thanks for the heads-up.  I'll look for that upload.  -Bill

Anonymous
Not applicable

Looking forward to the new version!

Cheers

rwunderlich
Partner Ambassador/MVP
Partner Ambassador/MVP
Author

The update, V1.12, is posted to the download page

http://robwunderlich.com/downloads/

-Rob

Anonymous
Not applicable

Hi Rob

Just a quick note to say I used v1.12 yesterday and it is fantastic. Great document!!!

Many thanks

Robbie