Here we will explore a Qlik Sense app that analyzes IoT data. There is “much ado” made of the new technology trend, the Internet of Things, otherwise known as IoT. Google defines the Internet of Things as
The interconnection via the Internet of computing devices embedded in everyday objects, enabling them to send and receive data.
Statista predicts that by 2020, IoT embedded devices will surpass 50 billion units. So this is obviously a trend that is here to stay.
They Don’t Need Us
We are used to our personal devices that provide directions or relay the news to us.
Continue reading Qlik Sense & the Internet of Things (IoT) [Example App] at Living Qlik.
This article was written using Qlik Sense version 3.1 as reference.
Let me first say that Qlik Sense is growing on me. Every version gives me a few more “Wish List” items that bring it closer to the functionality of QlikView.
At this point, the needle that judges Qlik Sense against QlikView that used to be decidedly leaning towards QlikView seems to be slightly tilting toward Qlik Sense.
I am aware that some of the features below have already been added by the use of extensions from the greater Qlik ecosystem especially over at Qlik Branch.
Continue reading 16 Items on My Qlik Sense Wishlist at Living Qlik.
What Qlik developer has NOT run into challenges involving separate fact tables and synthetic keys. Today, we will explore a version of this problem and the 2 best solutions for solving it, using a link table or concatenating the 2 tables together. In addition, we throw in the issue that the two fact tables differ in granularity.
The Teacher Becomes the Student
Let me first admit that this was a total learning exercise for me. I have taught a regular development class for a specific client using an unchanging set of materials for some years now.
Continue reading Qlik Roots: Link Table vs. Concatenation – A Case of Mixed Granularity at Living Qlik.