Qlik Sense Document Analyzer V1.5

Version 1.5 of the Qlik Sense Document Analyzer (QSDA) tool is now available for download here.

If you are not familiar with QSDA, it’s a free application profiling tool for Qlik Sense that can help you identify items such as unused fields, poorly performing expressions and data model problems.

Here are the significant changes in V1.5:

The Installer allows editing of all install paths and installation will create a log file in the User’s temp directory.

The  Summary ribbon at top of each sheet provides for sheet navigation by clicking a cell.

 

Improved error handling in the connector. Certain types of errors, such as a chart calculation timeout, will not terminate the script. Error count is reported on Summary sheet and detailed error messages can be viewed on the “Extract Log” sheet.

Items that should be considered incomplete due to analysis errors will highlighted in yellow.  This highlighting is a work-in-progress as I discover new possible errors.

Field widths (Symbol width) are no longer estimated! Field sizes are obtained directly from the engine.  Due to this change, this version will report different values for field sizes than previous releases, generally +/- 10%.

The connector edit dialog has been improved.  Error messages now appear properly in their own window and a progress bar displays when the list of applications is fetching.

If you have general usage questions on QSDA, please use the comments section here or Qlik Community.

If you have a bug to report, use the issue tracker.

The only installation supported by the installer is QS Desktop. You can use QS Desktop to analyze applications on a server.  It is possible to manually install on a server by uploading the application (qvf), the qsda-ribbon extension and the connector directory if you have the need and want to give it a shot.  I do plan to create a supported server installer in the future.

Have fun!

-Rob

Share

9 thoughts on “Qlik Sense Document Analyzer V1.5”

  1. Thanks for this Rob – great resource-again
    one question – the ribbon extension that is used qsda-ribbon
    It’s very neat – I take it this was installed with the exe file?

    I see the extension in my pc and the qvf file but not in QS as a useable extension in other apps?

  2. The ribbon extension is installed as a normal extension but hidden from the Custom Charts > Extensions list. I wanted to discourage people from using it for their own apps as I did not want to support compatibility between releases of DA. If there is interest I’ll create an open source version of the extension.

  3. It would be great to run it in batch across our whole server environment so we can identify problem apps?

    1. There is some work being done on batch analysis of multiple apps. Will post more as info becomes available.

  4. Hi Rob, first of all thank you for this great tool.

    We recently changed our default virtual proxy (No prefix) from NTLM to SAML authentication to take advantage of SSO using google business accounts.

    The NTLM authentication is still available using server_name/domain , and I tried to use that in the server string on appmeta connection but QSDA doesn’t seem to like this.

    Is there an alternative config so the tool works using the right Virtual Proxy?

    1. It should connect to the virtual proxy if you specify the proxy as part of the server like: “my.server/prox”. What error message are you getting?

      1. Hi, I’m getting

        ERROR: Cannot connect to Qlik Sense
        Connection failed after 4 attempts. Error message:
        GeneralCommunicationException with communication error WebSocketConnectionNotAccepted and http error code 500.

        In case it helps, if I run a data load anyway, it logs the following in stacktrace.txt (The txt is a bit too big to paste here)
        https://pastebin.com/MEqYDtg2

        1. Yes, the load won’t work because it uses the same connection methods that the connection editor does. I’m going to give you a qualified “don’t know” answer to this problem. You might try connecting to the same proxy in another browser tab and then try editing the connection in a another tab in the same window. More robust server connection and diagnosis is on the roadmap for the next update.

  5. Oh, I’m getting the error using QS Desktop

    I’d try to test it directly from the Server but I don’t know how to install the custom connector there

    Cheers

Leave a Reply

Your email address will not be published. Required fields are marked *