Power Tools 1.2 for QlikView

[StefanBackstrand]

Power Tools for QlikView

Version: 1.2

Download here

https://www.dropbox.com/sh/8hac72aljgqlr7d/AAASkzbM2H1OoVcLE_wa0kWGa?dl=0

For the absolute latest version, please see Power Tools for QlikView - One-stop-shop

In this release:

• QlikView Server Agent *updated* - 1.6.2
• QlikView Server Super Agent *updated* - 1.7.2
• QMS API Client - 1.0
• Qvs Detector - 0.9
• Qv User Manager *updated* - 1.0.1
• Reload Schedule Migration - 1.0.4321
• Server Object Handler *updated* - 2.0 - Updated to 2.1 @ 2014-03-18 11:00
• Server Object Handler Batch *updated* - 2.0
• Shared File Viewer *updated* - 1.5.2 - Updated to 1.5.3 @ 2014-02-21 09:32
• Qv Server Object Connector *updated* - 1.5
• XML Db Viewer - 1.0.4321
• Shared File Repair *new* and *updated* - 1.1 - Updated to 1.2 @ 2014-06-30 21:29

Release notes here: Power Tools 1.2 for QlikView - Release Notes

Readme here: Power Tools 1.2 for QlikView - Readme

Patches

• Shared File Viewer: Fixed broken "Color on top" sort option, new version 1.5.3
• Server Object Handler: Fixed credentials being passed wrong, causing no documents to show in list, new version 2.1
• Shared File Repair: Fixed "The path is not of a legal form" error when selecting Qvs binary, added "Don't show this" option in startup notification, fixed fonts", new version 1.2

Want to collaborate?

Do you have questions, thoughts or suggestions? Maybe you want to report a defect in the Power Tools? Please post it in the Management forum on QlikCommunity: http://community.qlik.com/community/discussion-forums/management

Also check out our Twitter: @QvPowerTools

DISCLAIMER

Power Tools are a collection of software programs and tools used for troubleshooting purposes only. Power Tools are provided free of charge and are not supported. Power Tools are not official QlikView products and are provided without warranty. Use of Power Tools is entirely at the user's own risk.

[StefanBackstrand]

Pablo,

I suspect that the exception you get when using the "Sheet Objects" view is merely a symptom.

I would suggest to firstly one thing:

1. Open the .shared file in Shared File Viewer. When open, select the option "Color on top" in the bottom right corner. If there are any red/pink objects that appear in the top of the list, there might be some issues with these objects, and we would like to know what.

Edit: I removed another suggestion, since it might be a bad idea. Sorry for that.

[pablolabbe]

Stefan,

  Selected the option "Color on Top", but no colored line is displayed. Also the menu item "Menu>Save Repair File" is disable. I think it doesn´t recognize as a defected shared file.

[Anonymous]

Quick suggestion...the QvServerObjectConnector tool does a great job for telling me what fields (dimensions and expressions) are in charts, but I don't see a way to tell what fields are in a TableBox.

If possible, I'd add that functionality to my wish list.

[Emmanuelle__Bustos]

Excellent Thank you So Much!!!

[vgutkovsky]

Hi, Stefan. Any luck with the CAL removal problem?

Thanks,

Vlad

[#7]

I've the following error while trying to run tools from pack. I've installed .NET Framework 4.0 on the server.

On the another server with 3.5 version all works fine

System.IO.FileNotFoundException: Could not load file or assembly 'System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified.

File name: 'System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'

   at XMLDBViewer.MainForm.OpenDatabase(String databasePath)

   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)

   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)

   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)

   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)

   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)

   at System.Windows.Forms.Control.WndProc(Message& m)

   at System.Windows.Forms.ToolStrip.WndProc(Message& m)

   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

WRN: Assembly binding logging is turned OFF.

To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.

Note: There is some performance penalty associated with assembly bind failure logging.

To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

[#8]

Does anyone know of a way that a Powershell script could call the SharedFileViewer inline, and export the xml contents of a large number (600+) of .SHARED files via a coded loop, rather than having to do each one by hand? I couldn't find an API for it in the README.

Thanks,

James

[StefanBackstrand]

It's not in the documentation yet, but the syntax is the following:

QvSharedFileViewer.exe sharedFilePath -EXPORTALL|EXPORTBOOKMARKS outputXmlFilePath

Examples:

QvSharedFileViewer.exe "C:\Documents\MyDocFile.shared" -EXPORTALL"C:\Documents\MyDocFile-Objects.xml"

QvSharedFileViewer.exe "C:\Documents\MyDocFile.shared" -EXPORTBOOKMARKS "C:\Documents\MyDocFile-Bookmarks.xml"

[#10]

Hi Stefan,

Thanks for the help! I tried it out, and was able to open QvSharedFileViewer.exe from the Powershell console, with a specific .SHARED file loaded as you said, with something like the following:

QvSharedFileViewer.exe "c:\Documents\MyDocFile.shared

But when I tried adding the Export commands to it, and running something like the following:

QvSharedFileViewer.exe "c:\Documents\MyDocFile.shared" -EXPORTBOOKMARKS "c:\Documents\MyDocFile-Bookmarks.xml"

it would just open the QvSharedFileViewer but with no file loaded in this time.

Any further suggestions as to why this might be?

Many thanks,

James

[vgutkovsky]

Stefan, after speaking with some other Qlik folks, it seems that this is a known bug with no fix in sight. Can you confirm? Got a client that needs this functionality.

Thanks,

Vlad