This is first in series of specific blogs that I will be writing explaining the fundamentals of Data Modelling in Qlik.
Data Model is the heart of your Qlik dashboard and can affect each of the following:
- Expression Complexity
- Reload Times
Link Table design and Star Schema are the most favoured data models and we shall be covering both of these in these blogs.
I plan to take the reader through a series of practical exercises that shall demonstrate the various concepts. The initial exercises shall be trivial since the blog is being written for the absolute newbie but as we proceed, I shall be bringing in more and more complexities.
In each of these exercises it is my recommendation that before looking at the solution provided by me, try to solve the same on your own.
Incidentally I am assuming that all readers are familiar with ETL scripting on Qlik. This blog does not cover any concepts related to ETL scripting.
The source system has the following three tables. Create a Data Model in QlikView for the same.
In Technoforte, we have encountered situations which required multi-node setup on QlikSense for some of our clients and we faced some problems while doing the multi node setup. This blog summarizes the steps to be followed as well as our learning on this subject.
Multi Node setup is much needed in such cases, where there is an overload on the machine where QlikSense Server is setup either due to frequent data load, or due to concurrently huge number of users accessing the Apps. QlikSense provides a very powerful feature of setting up the QlikSense Server on two or more machines, where workloads can be shared across the machines.
The first case where we had to carry out a multi-node setup, required a two node setup, where Node A would be the Central Node and Node B would be the Scheduler Node (all reload tasks would be taken care by this node).
There are couple of things you need to make sure before starting the multi node installation.
⦁ Ensure both the machines are able to communicate with each other. Make sure both the machines should be able to ping each other using the host name.
⦁ Please make sure both the machines have identical ODBC connections. If data is picked from a folder, then make sure the data files should be on the same path e.g. C:/QlikSense/Data.
Steps to Follow:
Below are the steps which you need to follow for doing Multi Node setup of QlikSense.
⦁ We shall assume here that QlikSense is already up and running on Node A (or the Central Node). (more…)
Nprinting is a recent acquisition by Qlik and the product is used for exporting and publishing reports from QlikView Dashboards. Amongst the limitations that NPrinting imposes on usage of various controls on QlikView dashboard, the most limiting constraint is the usage of Alternate States in QlikView. “Alternate States” is a very common requirement across Business Functions and it becomes almost impossible to deliver some of the end user desired functionality if this feature cannot be used in QlikView Dashboards.
In a recent project of ours which involved NPrinting based reports, we had an end user functionality which would become absolutely meaningless without the usage of Alternate States. That’s when we figured out an alternative workaround on QlikView to deliver the functionality of Alternate States without actually using Alternate States. This way we were able to deliver an “Alternate State” kind of functionality on NPrinting as well.
To those who are not familiar with Alternate States, this functionality allows us to provide comparative analysis across different sets of selection on the same Dimension. As an example in the following screenshot the YearMonth field affects Chart 1 which shows the Revenue in those Year Months.
Likewise AlternateYearMonth field affects Chart 2 which shows the Revenue in YearMonths selected in AlternateYearMonth field. You may observe that the same measure (Revenue) is getting compared to different sets of value of the same Dimension (in this case YearMonth). (more…)
In the previous post we had a quick introduction to the challenges when dealing with Enterprise Mobility. You can find that post here. This post will deal with choosing between and installed application and a browser application.
What is an installed app?
An Installed app is something that is installed in the phone / tablet and is always available on the device. An installed app can be downloaded from the online app store such as Google’s Play Store, Apple’s App Store or Microsoft’s Windows Phone Store. Alternately installed apps can also be side loaded. Side loading refers to the practice of loading applications into the device that are not certified by the store or not downloaded from the store. Some device operating systems have restrictions on side loading. Prior to the advent of app stores all applications were side loaded.
From a technical stand point the installed app resides on the device and runs using the device’s capabilities exposed as APIs by the device operating system. (more…)
This is an introductory post for a series of posts on enterprise mobility.
With a proliferation of smart devices in the hands of consumers, individual expectations from enterprise applications have risen sharply. Users expect information to be accessible anytime, anywhere. Service levels expected from the enterprises have also risen with higher benchmarks. While technology has kept pace thanks to innovative consumer applications, enterprise applications face numerous challenges. Let us take a look at some key factors on deciding your enterprise mobility strategy. (more…)