topic Re: Qlik Sense Document Analyzer V1.1 Released in App Development

Qlik Sense Document Analyzer V1.1 Released

rwunderlich — Fri, 17 Nov 2017 05:06:40 GMT

Finally, finally, a Qlik Sense version of my popular "QV Document Analyzer" tool is released. It is available for download here:

QS Document Analyzer http://qlikviewcookbook.com/recipes/download-info/qs-document-analyzer/

The tool is provided as a setup.exe that requires windows admin permissions as it installs a custom Qlik script connector.

There are limitations in this release documented in the release notes and the "Introduction" sheet on the qvf.

I'm looking for feedback in terms of problems you may encounter or suggestions.

Let me know how it works out for you!

-Rob

http://masterssummit.com

http://qlikviewcookbook.com

Re: Qlik Sense Document Analyzer V1.1 Released

sunny_talwar — Fri, 17 Nov 2017 13:00:07 GMT

That is great news Rob... Thanks for getting this out.

Best,

Sunny

Re: Qlik Sense Document Analyzer V1.1 Released

nevets22 — Tue, 21 Nov 2017 00:39:08 GMT

Can't thank you enough for following up! I'll be sure to send you feedback once I get the opportunity to test it out. Thanks again!

Re: Qlik Sense Document Analyzer V1.1 Released

shraddha_g — Tue, 21 Nov 2017 05:18:20 GMT

Awesome!

Re: Qlik Sense Document Analyzer V1.1 Released

rwunderlich — Mon, 27 Nov 2017 18:51:14 GMT

A bug has been reported re Variables. Error in script

"String reference not set to an instance of a String"

occurs when a variable has no content. Workaround is to add content to the variable or delete the variable.

-Rob

Re: Qlik Sense Document Analyzer V1.1 Released

dyy — Tue, 28 Nov 2017 16:38:25 GMT

Thank you! Perfect timing. Now to get access to QS Desktop on my client's server and I am all set. Their app is too large to bring to my desktop.

Re: Qlik Sense Document Analyzer V1.1 Released

saurabh_handa — Mon, 04 Dec 2017 07:10:14 GMT

Thanks Rob!

I recently downloaded and installed this connector(v1.1) on November 2017 version.

I am having some concerns which are listed below:

1. In Memory sheet, Per User Memory is not reflecting correctly and giving 0.0 MB most of the times. We have learned from earlier Qlik published papers is that the RAM footprint of any App is 4 times the size of file and per user allocation is 10% of RAM

footprint. e.g. 500 MB is size of file than RAM footprint is 2000 MB + 200 MB per user onwards.

Is that still applicable? Because DA is not giving exact result.

2. In Fields sheets, Field in Use filter is not working. for example in below screenshot, Field In Use is set as Y but the table is still showing Y & N. Can we also get description for all the fields in Table like Symbol Width(est), Symbol Bytes(est), Total Fields Bytes(est)...

3. In Objects sheets, can we get a differentiation value between out of the box visuals and extensions?

For example, below screenshot, Object Type fields is showing name of all visuals but not differentiating extensions.

Re: Qlik Sense Document Analyzer V1.1 Released

dtr — Mon, 11 Dec 2017 21:03:07 GMT

Hey Rob, just wondering, is the analyzer taking into consideration selections or just an open everything is selected state on object calc time? I'm working at a client and all objects in the application have a trigger to require a minimum state of selections before the object calculates, and these default selections are driven by a mashup the application is used in. To replicate the defaults I added a sheet event trigger and the trigger works in app, but our calc times seem very low compared to expectation. They do seem higher than they would if the chart didnt calculate at all which most would be doing based on the trigger anyway, but I wanted to check with you directly on the behavior just in case we're missing something. If it is the case where it only takes a wide view and calculate all objects with no selections we need to rethink on our end how to effectively test the application.

Thanks

Damien@qlik

Re: Qlik Sense Document Analyzer V1.1 Released

dtr — Thu, 14 Dec 2017 17:41:44 GMT

Rob,

A few additional questions on issues we're running into. First, some fields which are currently most definitely in use in the application are being marked as not in use. The only thing we can determine is different about these fields is that QS added an =sign in front of the dimension within the tables. Would this cause this to be ignored? In addition I see that the expression parser is breaking down large expressions to avoid memory issues, but will this impact field matching if say the expression is broken into parts in the middle of a field name? I'm trying to test this out within the data model sampled for our test by removing = signs (where QS lets me and doesn't just re-add them) but we're definitely getting a lot of mismatch on the in use and I wanted to bring it to your attention. Thanks again, Damien

Re: Qlik Sense Document Analyzer V1.1 Released

rwunderlich — Sun, 17 Dec 2017 00:50:55 GMT

There is definitely something wrong with the memory figures as I see 0MB for your Totall Field Bytes figures. Regarding the 4x and 10% figures. Those are just estimates and DA gives much more accurate figures -- when it's working which it doesn't appear to in this case. If you want to work this out with me please contact me at Contact | Qlikview Cookbook

Re the Fields filter. I can see that's a bug that I will fix in the next update.

I'll look into the OOB objects vs Extensions question. Good suggestion.

-Rob

http://masterssummit.com

http://qlikviewcookbook.com

Re: Qlik Sense Document Analyzer V1.1 Released

rwunderlich — Sun, 17 Dec 2017 00:55:13 GMT

Hi Damien,

The current version of QS DA will calc the objects in the default (clear) selection state. Those objects with a calculation condition that requires selections will therefore not calculate. How are you applying a sheet trigger? With an extension?

-Rob

http://masterssummit.com

http://qlikviewcookbook.com

Re: Qlik Sense Document Analyzer V1.1 Released

rwunderlich — Sun, 17 Dec 2017 00:57:07 GMT

I'll test with an = in front of the fieldname to see if that's a bug. Also, the 1.1 version is only looking at dimension and measures, not expressions like reference lines.

The next version will move the field parsing into the connector which should improve the accuracy.

-Rob

http://masterssummit.com

http://qlikviewcookbook.com

Re: Qlik Sense Document Analyzer V1.1 Released

saurabh_handa — Mon, 08 Jan 2018 10:06:21 GMT

Thanks Rob, any tentative timelines by when the next version with fixes would be available?

Re: Qlik Sense Document Analyzer V1.1 Released

rwunderlich — Mon, 08 Jan 2018 18:44:29 GMT

‌Feb 1.

Rob

Re: Qlik Sense Document Analyzer V1.1 Released

dtr — Tue, 09 Jan 2018 21:45:35 GMT

Hi Rob, looking forward to the update. Client was very happy to here a new version is coming.

Thanks,

Damien

Re: Qlik Sense Document Analyzer V1.1 Released

dtr — Tue, 09 Jan 2018 21:53:44 GMT

I had thought I responded previously, but the actual deployed mashup drives default selections when accessing via mashup, and when accessing via QS app we use an extension based trigger object to apply the selections as a button. I attempted to use a sheet event trigger extension as well hoping that may be able to replicate selections being made when each sheet opened, but as your app treats as clear state that wouldn't necessarily work. And unfortunately the data model makes it impossible to have charts work without selections made due to an extensive and complex entitlement and impersonation system in place in the application. Long story short we could fake a user by reducing the data so there was only those options available, but reduced data will calculate quicker and produce false positives for good performance, or we try to find a way to mimic the selection being made . I'm going to be dedicating some time to figuring this one out so I look forward to your updated version, and will be working out some ways on my end to best mimic the data state we need, but if there is any chance for a future release to be able to include a trigger or set default selections that would be fantastic.

Thanks,

Damien

Re: Qlik Sense Document Analyzer V1.1 Released

rwunderlich — Tue, 09 Jan 2018 22:41:23 GMT

If your focus is performance and you want to apply user scenarios, take a look at the Qlik Sense Scalability Tools (Sense v3.x, June/September/November 2017) if you have not already. With the tool you can define selections and other user actions and get some performance timings.

So perhaps you can use Document Analyzer for structural information and the scalability tool for more sophisticated performance testing.

-Rob

Re: Qlik Sense Document Analyzer V1.1 Released

ravireddyk — Sun, 21 Jan 2018 23:46:47 GMT

Hi Rob,

Is there a way to know the what sheets ( Base sheets, community sheets or user sheets) were using calculations , i know there are calculations shown but i am looking by sheet name and there objects, expressions , dimensions and measure and sheet owner id or sheet owner name.

Can we expect this in next release or any work around on this question for future purpose and also any thoughts on server level implementation of document analyzer.

Thanks,

Ravi

Re: Qlik Sense Document Analyzer V1.1 Released

rwunderlich — Mon, 22 Jan 2018 17:28:15 GMT

Hi Ravinder,

The table on the Objects sheet does show what sheet the object is on. Is that enough or are you looking for something else?

I'll need to get back to you on the Server question. I don't have a timeline for that yet.

-Rob

Re: Qlik Sense Document Analyzer V1.1 Released

Danijel — Thu, 01 Feb 2018 16:07:02 GMT

rwunderlich‌

Really great App! Unfortunatelly i got one Error, but i could not find the reason for that.

Maybe you can help me?

System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.

bei A.a.e.MoveNext()

bei QlikView.Qvx.QvxLibrary.QvxConnection.WriteTableItemsToStream(QvxDataTable table, Stream pipeStream)

bei QlikView.Qvx.QvxLibrary.QvxConnection.InternalExecute(DataPipe dataPipe, QvxDataTable table, Action`1 onError, Action clearMExecuteError)

Tested on Qlik Sense November 2017..

Thanks..