Hi,

I have seen many posts on community for showing negative values on charts like Block chart, pie chart etc. There is a solution available on community, but I thought to create the document so that everyone can utilize the same.

Lets say I have below data set

LOAD * INLINE [
Country, Score
US, 4971.765
UK, 4782.54
Japan, -200.941
India, 1412.181
Russia, 2445.292
];

Now I want to create the Block chart with above data set. So create the block chart with dimension as country and expression as sum(Score) , as soon as you create the chart you will get the error message that "positive and negative values in chart". But you can still display the negative values on chart with slight modification in expression.

Steps to create the block chart with negative value

1) Create the block chart

   Dimension : Country

   Expression : dual(sum(Score),fabs(sum(Score)))

If you want to display the distribution in % then use below expression

dual(num(sum(Score)/sum(TOTAL Score),'#0.00%'),fabs(sum(Score)))

Using dual function you can display the negative value with the base as positive value.

2) Go to chart properties -> Number Tab and check the Number format setting always as "Expression default". If the number format setting is not the expression default then negative values will be displayed as positive and also data will be displayed in wrong format. So if you want to provide any format like %, money you can define in the Dual expression itself using num function

Please see the attached application. In this application I have used the Fast change option so that you can see the results for multiple chart type as well

see also,

Control Chart

Benford's law

Bollinger Bands

Rolling N months

Regards,

Kushal

Year, Quarter, Month and Week To Date are the common analysis that I seen many applications. I will share the expression to do here

First to do this your data model should have the DateField in number format by applying floor

Similar to this

Floor(DateField) AS DateNum //it will gives you one whole number to represent date

YTD - Year To Date

A date should be selected and it will look for the Starting date of the year to the selected date.

Ex: date selected is 21-03-2014 then YTD is 01-01-2014 to 21-03-2014

Expression would be

Sum({<Year=, Month=, Quarter=, Week=, DateField=, DateNum={">=$(=Num(YearStart(Max(DateNum))))<=$(=Max(DateNum))"}>} Sales)

QTD- Quarter to Date

In the place of year use Quarter

Sum({<Year=, Month=, Quarter=, Week=, DateField=, DateNum={">=$(=Num(QuarterStart(Max(DateNum))))<=$(=Max(DateNum))"}>} Sales)

MTD- Month to Date

Sum({<Year=, Month=, Quarter=, Week=, DateField=, DateNum={">=$(=Num(MonthStart(Max(DateNum))))<=$(=Max(DateNum))"}>} Sales)

WTD- Week to Date

Sum({<Year=, Month=, Quarter=, Week=, DateField=, DateNum={">=$(=Num(WeekStart(Max(DateNum))))<=$(=Max(DateNum))"}>} Sales)

if you want you can set a variable value as 'Year', 'Month', 'Quarter', 'Week', lets say vToDate and go with single chart and single expression

Sum({<Year=, Month=, Quarter=, Week=, DateField=, DateNum={">=$(=Num($(=vToDate& 'Start(Max(DateNum))')))<=$(=Max(DateNum))"}>} Sales)

Will keep your expression simple

Regards,

Celambarasan

Hi all,

Qlikview Server has a number of licenses (AssignedCals), there may be a problem when these licenses come to the limit.

To avoid to click 200 times (delete foreach user, apply and then restore and applies again....) I create this simple program.

Launch the program (you need to be in the same network of Qlikview Server), enter the name of the QlikView Server and the number of the port (you can see these info in the address of the "QlikView Management Console"), once you have entered this information, the program connects to the Management Console and allows with few clicks to "clean" all licenses .

Work with latest Qlikview Server version (12.x).

[UPDATE 02-2017]

The latest version do all automatically (cancel and restore), and finally the program closes.

So once you open the program, just wait.

Bye,

emakio

Following a number of requests from Partners and New Joiners last year I've created a number of different QlikView templates which can get you started quickly. The focus has been on setting the framework to allow you to create applications quickly and easily that look modern and professional. Don't forget our QlikView Developers Toolkit which has a wealth of backgrounds, buttons and icons to assist you.

Enjoy.

Last week I got a question to get number of working days between two dates

1. Excluding Public Holidays
2. Including Saturday as Half Working Day
3. Including Saturday as Full Working Day.

Have done some work and created enclosed QlikView File.

Suggestion and Correction would be highly appreciated !

Hi,

I just wanted to share another example on how to create a Gantt chart in QlikView. To do this we can use some of QlikView's available resources as an alternative to the use of Extension Objects. In this case I have used a Pivot Table.

To create this chart I’ve used some example data (Excel file) that can be found on the zip file attached bellow. That file has several fields, enough to identify the tasks of a Project (such as ID, Start, End…).

In order to be able to pick the desired dates a master calendar has been used. Also, the IntervalMatch functionality has proved very useful by generating the dates between the start and end of the different tasks that the project has.

The Hierarchy functionality in the load script generates the different task levels.

There is something peculiar about the data I am using (Excel file). Colors for each task are specified in Hexadecimal format. So during the load script I converted them to RGB colors (color code used by QlikView).

After the data model has been completed a Pivot Table can be used to represent my Gantt chart. To make the chart stable, on the pivot table properties we need to uncheck the "allow pivoting" option. As dimensions we will have each task level, years months and days.

The expression is a bit different. First of all, I it's represented as an Image. That image is a png file (included in the zip file) with transparency that will let us see the background color of each cell.

The expression is as follows:

if(End=Start,'◆',
      if(date(DateID)=date(Today()),'gantt_part_today.png',
           if(Start = DateID and Group = 1,'gantt_part_end_l.png',
                if(End = DateID and Group = 1,'gantt_part_end_r.png',
                     if(End-DateID+1>0,'gantt_part_mid.png',
                          if(date(DateID)=date(Today()),'gantt_part_today.png'))))))

The background color for each cell is already stored in the data. So we just need to use it as a background color for our expression. In this case, if it is not a milestone, use the color value:

if(Mile =0, RGBColor)

That's all. The Pivot table now can be used as Gantt chart. I hope you find this example useful.

This document shows the Difference between "Sum of Rows" and "Expression Total". Also how this can be implemented in Straight Table and Pivot Table in QlikView.

Hope this would be helpful for beginners.

Thanks,

Nisha

Power Tools for QlikView

Version: 1.3.2

..again! A small update of one tool, and test of another.

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

QlikView 12.X support matrix

Reviewed/updated with support for QlikView 12

• QlikView Server Agent *tested* - 1.6.2 - supported
• QlikView Server Super Agent *updated*- 1.7.3 - supported

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

Readme here: Power Tools 1.3.2 for QlikView - Readme

Want to collaborate?

Do you have questions, thoughts, suggestions or bugs to report on Power Tools? Please post in the forums on QlikCommunity: https://community.qlik.com/community/qlikview/management

Also check out our (currently dead, soon to be revived) 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.

Hi Qlikers,

Firstly, kudos to avinashelite‌ for giving us the below method to load the all excel files with the multiple sheets.

Loading Multiple Excel Sheets Dynamically along with file name and sheet name

Using above method we can load the multiple excel files with multiple sheets even though all the sheets have different names.

Above method  works only in below scenarios

1)  When all the files having the same number of sheets.

2)  When all the sheets of excel files having the same number of Columns with same name.

But below method works even though you don't have same number of columns and sheets in excel and having blank sheet in excel.

// Define the Path

LET vExcelFilePath = 'D:\Test';
LET vQVDFilePath='D:\Test';

SUB CreateQVDFromAllExcelFiles(vPath)

FOR EACH vFileExtension IN 'xlsx'

FOR EACH vFile IN FILELIST(vPath & '\*.' & vFileExtension);

ODBC CONNECT TO [Excel Files;DBQ=$(vFile)];

Temp:
LOAD *;
SQLtables;
DISCONNECT;

Data:
LOAD * INLINE [
junk ];

FOR i = 0 TO NOOFROWS('Temp')-1

LET vSheetName = PURGECHAR(PURGECHAR(PEEK('TABLE_NAME', i, 'Temp'), CHR(39)), CHR(36));

CONCATENATE(Data)
LOAD  *,
FILEBASENAME() AS FileName,
'$(vSheetName)' AS Sheet_name
FROM $(vFile)(ooxml, embedded labels, table is [$(vSheetName)]);

NEXT i

DROP TABLE Temp;
DROP FIELD junk;

NEXT vFile
NEXT vFileExtension

Set ErrorMode=0;
Drop Field A;     // When there is blank sheet in excel file, field A is created
Set ErrorMode=1;

STORE Data into $(vQVDFilePath)\FullData.qvd;
DROP Table Data;

END SUB

CALL CreateQVDFromAllExcelFiles('$(vExcelFilePath)');

LET i = Null();

Feel free to provide your suggestions

Thanks & Regards,

Kushal Chawda

Greetings,

For the longest time, I have been trying to improve the quality of an exported image out of Qlikview.  Sometimes my end users want to just copy an image to the clipboard and paste it into an e-mail or a Word document.  By default these images export with less than desirable quality.  In particular, I use Nprinting and the image quality was so poor, we almost could not use the application.

Well, sometime a blind squirrel finds a nut or in my case the lottery ticket that wins you a millions dollars.

There is a setting in the User Preferences in Qlikview called Clipboard Zoom.  See attached Word Document.  By default, this setting is at 100 % in order to minimize the file size of the output.  This also leads to less than desirable quality.  I included an image from the sample surgical dashboard at 100 %.  I then change the setting to 400 % and copied the image to the clipboard and pasted the same image to the Word document   The results are astounding.  If you view the 400 % file, you can enlarge it and still get good quality.  The only sacrifice is that the file size of the image is substantially bigger.  I will gladly trade file size for image quality.

Try zooming on the images in the Word document.  It is night and day difference.

Now, here is the tricky part.  The setting is a User Preference.   So, even if I change it on my developers machine, I need to make sure the setting is changed on my end users desktop client.   If you are using Nprinting, you can specify the user name and password when you are connecting to the source data.

As a general rule, you should probably size your objects in Qlikview about the same size that you would like to appear in your external document after you export it.  This will minimize possible distortion as you scale it further.

I hope this post is helpful for you today.

Mike Czerwonky

BI Developer

Once loading data into the QlikView script/application, data validation becomes one of the first tasks to accomplish. Here, I have provided a simple was in order to build a data validation sheet in order to analyze data by selecting table and field. The ability to obtain statistics for the field and values, make it easier in order to perform simple data quality checks.

You can download this script and copy the QlikView Objects within your own script/application:

Dear Community,

I am sharing this document as I was always searching for list of all Qlik Chart functions in order for learning purpose. I couldn't find so I have created a list of all the chart functions available in Qlik. All the functions are available in Qlik but just in case if you want an ordered list.

I hope this will be helpful. 

Best Regards,

Arpit Vijay

https://www.linkedin.com/in/arpitv/

Dear Community,

Please find a new document explaining the LOAD command.

This document was first the content of personal notes. It has become bigger and bigger: I just hope it is not too big. it contains 60 pages: let's say that there is almost a tutorial even if there is no exercice.

Basic syntax is first explained but less basic syntax is also reviewed.

Please enjoy ...

Fabrice

PS. compared to version 1, I took into account HIC' comment and added two sections: INPUTFIELD (to enter some data into QlikView) and Generate Random Data (for test purposes)

Hi everyone,

as described in How to show or visualize this kind of data? I found heatcharts to be very effective in cases of visualization of numeric facts by two dimensions with lots of values each.

To do so, I would create a pivot table with dimensions e.g. department and organism name an add the # of organisms as an expression. Then by draging the department dimension to the top of the chart you can create one column per department each. The # of organisms then would be used to color code the background color (expression tab of the charts properties).

The result should look like this:

By sorting the organism and department dimensions using the # of organisms expression (descending) you can bring the most infectious of your organisms to the top of the table and the most involved departments to the left side.

This also allows for your users to focus on these specific departments and organisms:

Hope this could be useful

regards

Marco

A QlikView Technology White Paper

Published: November, 2011

www.qlik.com

Introduction

Event Driven Execution (EDX) allows the running of QlikView batch jobs based on external events. The primary usage of EDX is to have an external scheduler or Extract,Transform, and Load (ETL) tool (for example, Informatica) run QlikView batch jobs as part of a larger batch process. There are also other use cases, forexample, triggering a QlikView batch when a file arrives and user-initiated batches. This document describes the requirements for each of these three use cases.

The example code (attached below as QMSEDX-v1.exe) and executable (attached below as QMSEDX_CommandLine_v1.exe) that is delivered together with this document uses the new EDX API, which means this document and the example code are useful both when using the EDX functionality for the first time and when migrating from previous versionsof the EDX API.

Use Cases

Using an External Scheduler or ETL Tool

Many large organizations have other batch requirements than just QlikView. Such organizations often use a standard tool to run all batch processes, so that the IT training costs are minimized and common operations (for example, logging and re-launching) are handled in one central place. In addition, QlikView batch processing is almost always reliant on new data being available and in many cases this data is created by other batch processes. An external scheduler or ETL tool can be used to prepare the data and then run the QlikView batch to load it.

Most scheduler and ETL tools are designed to run external batch programs via a command line interface. The reasons for this include:

• Batch processes are long-running, so starting aseparate process to handle them provides a simple way for the scheduler tomonitor the batch processes.
• The scheduler can be configured to run the batchusing a particular operating system account that provides the required securitycontext.
• If the batch process fails, the standard operatingsystem error handler can be used to pass this information back to the scheduleror ETL tool.

The main alternative to using a command line tool is using some sort of web services. Unfortunately,web calls cannot be used for long-running processes, since a timeout eventually occurs. A common solution to this problem is to start the process with a web request and then follow it up regularly with subsequent requests to find out if the original request has finished successfully or not.

File Arrival Detection

In many IT departments, the inter-system communication is not orchestrated by ETL or even Enterprise Application Integration (EAI) tools. Instead, files are pushed. For example, a non‑QlikView batch job that extracts data from a production database is typically owned by the IT team running the database, which means the team is responsible for creating and configuring the batch job and ensuring that it runs correctly.On the QlikView side, a program that checks if a file has arrived must be running, so that the file can be used in a subsequent QlikView batch.

In this scenario, simply starting the QlikView batch process should be enough. There is no need to follow its execution. The program is typically a Windows service as it runs all the time.

User-initiated Action

TheQlikView Automation API provides a number of functions that run QlikView batch scripts, for example, Document.Reload(). However, it is normally not a good idea to let users run batch jobs, since a QlikView batch job typically replaces the entire data set of an application used by many users.This means a single user can interfere with the work of all the others unless the QlikView batch is carefully configured. Because of this, the batch functionality is disabled in a QlikView Server deployment.

• The marketing department at a pharmaceutica lcompany has an organizational division between the analysts and the product managers. The analysts are in charge of loading a dozen external data sources of varying quality. Once the data relating to a particular product is ready, the running of a QlikView batch loads the data and publishes the application to the relevant product managers.
• A software company with thousands of employees wants each employee to have access to their sales data up to the last 30 minutes. The computer resources needed to support such data usage are massive. Since the salespeople only use the system once a week on average, it is decided to allow each user to run a QlikView batch to generate a QVW (for the user)whenever needed.

EDX in QlikView 11

In QlikView 11, EDX runs through the QlikView Management Service (QMS) API. This is a major change from QlikView 10, where EDX is realized by calls directly to a QlikView Distribution Service (QDS). The QMS API is a web service API that uses theSimple Object Access Protocol (SOAP). Client applications make HTTP (web) requests to QMS on port 4799. The system is secured by NT LAN Manager (NTLM) as well as special protective measures to avoid certain types of hijacking attacks known as “time limited service key”. This combination of security means the client application must be written in .NET and therefore the provided example code is .NET projects/solutions developed in Microsoft Visual Studio 2010.

The client application uses NTLM to authenticate a Windows account to QMS. QMS then checks which Windows groups the Windows account for the client application is member of to determine the function calls the user is allowed to make. Most of the QMS API requires membership in a local group called “QlikView Management API”, but to run EDX, a separate group, “QlikView EDX”, should be used. Both groups are local Windows groups on the server where QMS runs.

The client application makes calls to instruct QMS to start a task and in return receives an error code indicating success or failure, as well as an execution ID. The execution ID uniquely identifies the execution of the task as opposed to the task itself. The client application then periodically polls QMS to check the progress of the task execution. This poll request returns a data structure that contains, among other things, the execution status, start time, stop time (if already finished), and a list of new execution IDs. These subsequent execution IDs represent the execution of tasks that are triggered because the initial task has finished. The client application can then follow an entire set of inter-related tasks that together make up a full parallelized batch flow.

Lastly, the example code outputs log information and returns an error code to the operating system. The error code can be recovered in a standard way, for example, by using the %ERRORLEVEL% environment variable in a BAT file.

Changes Compared to Previous Versions

From a functionality perspective, the following has changed compared to using EDX in QlikView 10:

• Because communication is with QMS instead of QDS, a QDS cluster can be used to load balance EDX calls. If high availability is required for the batch environment, QMS is a single point of failure. Consider either virtualization of QMS or an active/passive system.
• The overall success or failure code of aQlikView batch can be returned. Previously, the status of the task could be fetched (that is, the definition of the batch job), but not the execution ofthe batch job.
• The execution of subsequent tasks can be followed.

Notes on Using the QMS API

Finally,some notes on using the QMS API in QlikView 11:

• The EDX password must not be null. Use an empty string, if no password is configured.
• The QDS ID is required in the function call that starts the EDX batch job. However, higher-level privileges than membership in “QlikView EDX” are required to get a QDS ID. The simple solution is to pass an empty GUID for the QDS ID, which means QMS will search for the task in all configured QDS instances. Almost all projects today only have one logical QDS configured, so this can be a useful solution.
• EDX can be used without a QlikView Publisher license. Simply pass the name of the QVW instead of a task name and the reloadschedule of the QVW will run.

Hi Everyone,

Here you will find a solution to a problem that I have tried to solve this week, and that could be useful in every Qlik infrastructure.

For anyone who has tried to get a global view of the Qlik services states, here is the solution I found.

@marcus_sommer I thought this might interest you

1.

• Create a Powershell script (.Ps1) that loop on a list of servers that you define.
• Get the state of every Qlik service.
• Verify if that state if Running or not.
• Prepare the csv file structure (Date, Server, Service, State) and export it.

       * with "append" option to be able to schedule the script to run at a certain frequency on a day and don't lose the lines created each time.

2.

• Create a .BAT file that calls Powershell.exe to launch the (Ps1) file.
• Schedule it using the Windows Task scheduler or the QMC.

Below the Powershell Script:

#Define a list of servers
$servers = @("xxx-xxx-xxx","xxx-xxx-xxx","xxx-xxx-xxx"...)

#Loop on the servers defined above
foreach ($server in $servers) {

    #Get the actual date
    $getDate = Get-Date

    #Get the state of all Qlik services
    $statusQlikviewDirectoryServiceConnector = (get-service "QlikviewDirectoryServiceConnector" -ComputerName $server).Status
    $statusQlikViewDistributionService       = (get-service "QlikViewDistributionService"       -ComputerName $server).Status
    $statusQlikviewManagementService         = (get-service "QlikviewManagementService"         -ComputerName $server).Status
    $statusQlikviewServer                    = (get-service "QlikviewServer"                    -ComputerName $server).Status
    $statusQlikViewSettingsService           = (get-service "QlikViewSettingsService"           -ComputerName $server).Status

    #Verify if the QlikviewDirectoryServiceConnector is Running
    if ($statusQlikviewDirectoryServiceConnector -eq "Running") {

        "$getDate $servers  QlikviewDirectoryServiceConnector is up"

        $vExportQlikviewDirectoryServiceConnector = @{
        Date=$getDate
        Server=$servers
        Service='QlikviewDirectoryServiceConnector'
        Status=$statusQlikviewDirectoryServiceConnector
         }
        $results = New-Object psobject -Property $vExportQlikviewDirectoryServiceConnector
        $results | Export-Csv -path C:\Temp\Powershell\Eventlogs.csv -NoTypeInformation -Append

    } 
    
    else {

        "$getDate $servers QlikviewDirectoryServiceConnector is down"

        $vExportQlikviewDirectoryServiceConnector = @{
        Date=$getDate
        Server=$servers
        Service='QlikviewDirectoryServiceConnector'
        Status=$statusQlikviewDirectoryServiceConnector
         }
        $results = New-Object psobject -Property $vExportQlikviewDirectoryServiceConnector
        $results | Export-Csv -path C:\Temp\Powershell\Eventlogs.csv -NoTypeInformation -Append

    }


    #Verify if the Service QlikViewDistributionService is Running
    if ($statusQlikViewDistributionService -eq "Running") {

        "$getDate $servers QlikViewDistributionService is up"

        $vExportQlikViewDistributionService = @{
        Date=$getDate
        Server=$servers
        Service='QlikViewDistributionService'
        Status=$statusQlikViewDistributionService
         }
        $results = New-Object psobject -Property $vExportQlikViewDistributionService
        $results | Export-Csv -path C:\Temp\Powershell\Eventlogs.csv -NoTypeInformation -Append

    } 
    
    else {

        "$getDate $servers QlikViewDistributionService is down"

        $vExportQlikViewDistributionService = @{
        Date=$getDate
        Server=$servers
        Service='QlikViewDistributionService'
        Status=$statusQlikViewDistributionService
         }
        $results = New-Object psobject -Property $vExportQlikViewDistributionService
        $results | Export-Csv -path C:\Temp\Powershell\Eventlogs.csv -NoTypeInformation -Append

    }


    #Verify if the service QlikviewManagementService is running
    if ($statusQlikviewManagementService -eq "Running") {

        "$getDate $servers QlikviewManagementService is up"

        $vExportQlikviewManagementService = @{
        Date=$getDate
        Server=$servers
        Service='QlikviewManagementService'
        Status=$statusQlikviewManagementService
         }
        $results = New-Object psobject -Property $vExportQlikviewManagementService
        $results | Export-Csv -path C:\Temp\Powershell\Eventlogs.csv -NoTypeInformation -Append

    } 
    
    else {

        "$getDate $servers QlikviewManagementService is down"

        $vExportQlikviewManagementService = @{
        Date=$getDate
        Server=$servers
        Service='QlikviewManagementService'
        Status=$statusQlikviewManagementService
         }
        $results = New-Object psobject -Property $vExportQlikviewManagementService
        $results | Export-Csv -path C:\Temp\Powershell\Eventlogs.csv -NoTypeInformation -Append

    }


    #Verify if the service QlikviewServer is Running
    if ($statusQlikviewServer -eq "Running") {

        "$getDate $servers QlikviewServer is up"

        $vExportQlikviewServer = @{
        Date=$getDate
        Server=$servers
        Service='QlikviewServer'
        Status=$statusQlikviewServer
         }
        $results = New-Object psobject -Property $vExportQlikviewServer
        $results | Export-Csv -path C:\Temp\Powershell\Eventlogs.csv -NoTypeInformation -Append

    } 
    
    else {

        "$getDate $servers QlikviewServer is down"

        $vExportQlikviewServer = @{
        Date=$getDate
        Server=$servers
        Service='QlikviewServer'
        Status=$statusQlikviewServer
         }
        $results = New-Object psobject -Property $vExportQlikviewServer
        $results | Export-Csv -path C:\Temp\Powershell\Eventlogs.csv -NoTypeInformation -Append

    }


    #Verify if the service QlikViewSettingsService is running
    if ($statusQlikViewSettingsService -eq "Running") {

        "$getDate $servers QlikViewSettingsService is up"

        $vExportQlikViewSettingsService = @{
        Date=$getDate
        Server=$servers
        Service='QlikViewSettingsService'
        Status=$statusQlikViewSettingsService
         }
        $results = New-Object psobject -Property $vExportQlikViewSettingsService
        $results | Export-Csv -path C:\Temp\Powershell\Eventlogs.csv -NoTypeInformation -Append

    } 
    
    else {

        "$getDate $servers QlikViewSettingsService is down"

        $vExportQlikViewSettingsService = @{
        Date=$getDate
        Server=$servers
        Service='QlikViewSettingsService'
        Status=$statusQlikViewSettingsService
         }
        $results = New-Object psobject -Property $vExportQlikViewSettingsService
        $results | Export-Csv -path C:\Temp\Powershell\Eventlogs.csv -NoTypeInformation -Append

    }

}

Here is the output of the file export using the script above:

"Date","Status","Server","Service"
"06/03/2019 17:22:34","Running","vw-d-rxx-05","QlikviewDirectoryServiceConnector"
"06/03/2019 17:22:34","Running","vw-d-rxx-05","QlikViewDistributionService"
"06/03/2019 17:22:34","Running","vw-d-rxx-05","QlikviewManagementService"
"06/03/2019 17:22:34","Running","vw-d-rxx-05","QlikviewServer"
"06/03/2019 17:22:34","Running","vw-d-rxx-05","QlikViewSettingsService"

If you need more details on how you run all this and get the schedueling done, don't hesitate to leave a comment or send me a direct message.

Have a great day !

Youssef

This example has been produced to accompany the blog post Sending Data In QlikView Alerts

There is a Qlik Sense version of this solution here: https://www.quickintelligence.co.uk/send-data-from-qlik-load-script/

This application demonstrates how alerts e-mails can be sent when a certain criteria is met.  It also takes this concept further by showing how the CONCAT and AGGR statements can be used to construct a string from a number of expressions, which can then be used as the body of the email.

The blog article gives further details and explanation on how this works and how to implement it in your own applications.

Please also see my other uploaded Qlik apps and tutorials https://www.quickintelligence.co.uk/examples/

Steve Dark

https://www.quickintelligence.co.uk/

This page will collect all relevant release information about Power Tools for QlikView, and will be continuously updated with each new release and with any patches that are issued. This way we hope for a more consolidated view of the Power Tools suite.

Do you have a feature request or a bug?

• Start a discussion in the QlikView Management or Deployment forums, or
• Email sbn@qlik.com

Latest release

Power Tools 1.3.2 for QlikView

Power Tools 1.3.2 for QlikView - Release Notes

Power Tools 1.3.2 for QlikView - Readme

QlikView 12 compatibility matrix

Please note that this matrix only describes the compatibility with QlikView 12. It does not indicate whether or not Power Tools are officially supported, because they are not.

SharedFileViewer

Provides insight into the QlikView Server .shared files belonging to .qvw documents. The .shared file stores server data such as server/shared bookmarks, server objects (charts and objects created by a client via the server), annotations and other data that is specific to the document. The tool visualizes the content of the binary .shared file and provides options to "Repair" legacy files, as well as defrag large .shared files.

QvServerObjectConnector

A custom data connector for QlikView that much like the SharedFileViewer provides insight into .shared files, but instead allows to load data straight from .shared files into QlikView documents for analysis. The tool supports extraction of data like ownership, size and type of objects, expressions, annotations, bookmark selections (fields and values) and much more.

QlikView Server Agent

A small service utility that allows easy management of QlikView services. Also allows for quick change of credentials across multiple services at the same time.

QlikView Server Super Agent

A monitoring tool for QlikView Server, that monitors Qv services regardless of version (9+) and reports any service outage with email notifications and/or log files.

QMS API Client

A highly useful tool that gives its user the possibility to interact with the complete setup of QMS API functions in QlikView Server without typing a line of code. Visualizes data structures and enables the user to parameterize and test every function call based on their own data or data from the QMS API.

Qv User Manager

A command-line tool to list, add, remove and edit CAL and user information in a QlikView Server remotely.

QvsDetector

Scans the current subnet for other QlikView Servers and visualizes information like license, root folder, version and such. Also enables certain administrative functions.

Reload Schedule Migration Tool

A small step-by-step instruction tool that helps migrate reload schedules from non-Publisher databases in 9 to Publisher databases in 10 or 11, by manipulating the QVPR database (XML repository required) directly.

Server Object Handler

Enables listing, ownership changing and deletion of server objects in documents hosted on a QlikView Server remotely. Also allows ownership changing to be performed on a selected number of server objects matching a given name pattern.

Server Object Handler Batch

The command-line little brother of the Server Object Handler, that does all the same, but from any command prompt or batch script.

XmlDbViewer

Visualizes and enables searching in and editing of the QlikView Publisher Repository database (QVPR), when in XML format.

Shared File Repair

Uses the upgraded .shared file verify and repair functionality that was re-introduced in QlikView Server (QVS.exe) SR5, by providing a GUI to execute verify/repair operations on one or more .shared files and report the result. Note that even though the verify/repair functionality first came into QVS in 11.20 SR4, this version requires the upgraded functionality in 11.20 SR5.

Frequently Asked Questions

Q: What is a Power Tool?

A: A Power Tool is a small utility program or application that aid in performing a specific functionality or that extends QlikView functionality in some other way.

Q: When should I use a Power Tool?

A: Power Tools should be used when there is a need for functionality that is not in the QlikView product suite already, to evaluate new functionality or when administrative actions outside that is not available as part of the regular program suite might be needed.

Q: Do I need to install any of the tools?

A: No, all tools are, as of this moment, drop-to-deploy tools. Be aware that some of them require resource files outside of the executable itself, like for example configuration files or DLL files. When deploying, make sure to deploy the whole folder and its content.

Q: Do the tools require administrative privileges?

A: Some of them require this, yes. It is up to each tool and its functionality. If you are using UAC (User Account Control) security, make sure to run the tools in privileged mode (right-click and select “Run as Administrator”).

Q: Is there any documentation for the Power Tools?

A: Yes. A limited documentation for the Power Tools is included in each of the separate tools.

Q: Are the Power Tools Supported?

A: No. The Power Tools are not supported and is seen as use-as-is tools, supplied separate from the QlikView product suite. *** Qlik is not responsible for any consequences such as environmental issues, data corruption, configuration errors or unexpected behavior, resulting from the use of Power Tools. ***

Q: Where do I report bugs in the Power Tools?

A: To report a bug, please visit our QlikCommunity Discussion Forums, for example the QlikView Management or QlikView Deploymentforums or send an email to SupportServiceabilityLabs@qlik.com. Bugs will be fixed between releases of the Power Tools entirely at Qlik's discretion.

Older versions

Power Tools 1.3.1

Power Tools 1.3.1 for QlikView

Power Tools 1.3.1 for QlikView - Release Notes

Power Tools 1.3.1 for QlikView - Readme

Power Tools 1.3.0

Power Tools 1.3.0 for QlikView

Power Tools 1.3.0 for QlikView - Release Notes

Power Tools 1.3.0 for QlikView - Readme

Power Tools 1.2

Power Tools 1.2 for QlikView

Power Tools 1.2 for QlikView - Release Notes

Power Tools 1.2 for QlikView - Readme

Power Tools 1.1

Power Tools 1.1 for QlikView

Power Tools 1.1 for QlikView - Release Notes

Power Tools 1.1 for QlikView - Readme

Power Tools 1.0

Power Tools 1.0 for QlikView

Power Tools 1.0 for QlikView - Readme