Hear directly from Qlik employees in our eight unique blogs. Check out the new Architecture Deep Dive Blog!
Important and useful support information about end-of-product support, new service releases, and general support topics.
Updates for Qlik Community offerings, announcements and changes.
All about product and Qlik solutions: scripting, data modeling, visual design, extensions, best practices, etc.
This forum was created for professors and students using Qlik within academia.
On this forum you can access and follow the latest updates of our courses and programs with the Qlik Education team.
Learn about what's new across all of the products in our growing Qlik product portfolio.
Information on all new product releases, connectors, beta programs, and technical product information.
Deep dives into specific back-end technologies which allow for the extension of Qlik to fit the needs of the enterprise.
All about Qliks Voice of the Customer program and Customer Success initiatives
QlikView Standard Visualization objects have much more to offer than standard out of the box settings. This is why data centric apps developers love QlikView so much, because you can dig into every object properties expanding their usage case scenarios.
This is the case of the line chart; probably one of the oldest visualization methods available. It´s a pretty simple and straightforward way to represent data - often used to visualize a trend in data over intervals of time.
This is a simple space saver trick; it will help you to replace QlikView standard legend with a customized in-chart legend.
Look at the chart below. It represent sales in two countries US and UK. As you can see, we don't have too much space to plot the chart and the legend. QlikView will automatically adjust the chart area to the real state in the object. In this case that will make my chart area to be really small.
One approach could be to move the legend to the bottom. This will make my chart area much bigger, specially true for long label scenarios. On the other side, by reducing the Y axis the lines look much flatter, and in some situations that could mean that some users wont perceive small variations in the chart.
Remember: To move or/and size chart components as legends, text in charts, and chart area, press the Shift and Ctrl keys and keep them depressed while a chart is active. You will enter the chart layout edit mode.
In edit mode, thin red rectangles will appear around those components of the chart that can be sized or moved. Use the mouse drag and drop technique to move things around.
Another alternative could be something like the chart below, where legends appear right next to the each line.
To tune a line chart to look like the image above, you will need to follow the next steps:
I will post a second part on this topic with another trick soon, stay tuned!
PS: if you have tricks you want to share with our Community left us a comment
Hopefully you’ve had a chance to learn about the latest exciting innovations we’ve made with our multi-cloud strategy in our April release. It included all of the capabilities needed to deploy Qlik Sense Enterprise entirely on Qlik Cloud Services (enterprise SaaS), as well as in a private cloud with Kubernetes, and/or in a hybrid scenario that combines both on-premise and cloud environments. Today, we offer you unparalleled choice in how you deploy analytics and migrate to the cloud. Most importantly, we are committed to supporting you on your cloud journey with you, whatever form it may take.
At Qonnections we really enjoyed hearing your questions and feedback. Based on what we heard, here’s a recap of the top five things you need to know about Qlik Sense Enterprise on Qlik Cloud Services:
The most important thing we want you to know is that Qlik Sense Enterprise on Qlik Cloud Services is available for you now.
Check out the video below by our own Mike Tarallo who takes you on a tour of some of the latest features and content management capabilities available in Qlik Sense Enterprise on Qlik Cloud Services.
Whenever you have a generic database, the Generic prefix can be used to transform the data and create the desired fields. A generic database is basically a table where the second last column is an arbitrary attribute and the very last is the value of the attribute. In the input table below you have a three-column generic database.
But if you want to analyze this data, it is much easier to have all attributes in separate fields so that you can make the appropriate selections. It is not very practical to have one single field for all attribute values, since you may want to make selections using different attributes at the same time.
Enter the Generic prefix.
It converts the data to a structure where each attribute is placed in a field of its own. Another way to express it is to say that it takes field values and converts these to field names. If you compare it to the Crosstable prefix, you will find that they in principle are each other’s inverses.
The syntax is
Generic Load Key, Attribute, Value From … ;
There are however a couple of things worth noting:
If you have more than one key, this means that you will get a composite key – a synthetic key – in the data model:
Although it looks ugly, this synthetic key is completely harmless. But it may still be a good idea to replace it with a manually created concatenated key:
Autonumber(Key1 & '|' & Key2 & '|' & Key3) as Key,
Finally, I have seen many examples on QlikCommunity where a For-Next loop is used to join together all tables created by the Generic prefix, e.g.:
Set vListOfTables = ;
For vTableNo = 0 to NoOfTables()
Let vTableName = TableName($(vTableNo)) ;
If Subfield(vTableName,'.',1)='GenericLabel' Then
Let vListOfTables = vListOfTables & If(Len(vListOfTables)>0,',') & Chr(39) & vTableName & Chr(39) ;
Load distinct Key From GenericDB;
For each vTableName in $(vListOfTables)
Left Join (CombinedGenericTable) Load * Resident [$(vTableName)];
Drop Table [$(vTableName)];
The result is one big table that contains all attributes; a table that often is sparse (containing many NULL values) and much larger than the initial tables. And no performance has been gained… So I can only say:
You should not do this - unless you have a specific reason to.
The Generic prefix creates a set of tables that store the data in an optimal way. In most cases you should not change this. I realize, however, that there are cases where you want to transform the data further and need the data in one, unified table. Then the above scriptlet can be used.
Hi guys! I'm super excited to invite you to our next Qlik Insider Webinar. In this video I give you the rundown on what to expect to see on our next webinar focusing on our September and November 2019 releases.
We keep innovating — so you can too. Register for the Qlik Insider Webinar Series to stay connected on our latest releases, and learn how you can benefit from the newest features in our platform.
Our next Qlik Insider Webinar is on November 20th.
Hello All Qlik Sense Users,
If you are using Core Based licenses, we have been alerted that a high number of end users are encountering the following error:
"You cannot access Qlik Sense because you have no access pass"
At this time, the issue is under investigation with our Internal Licensing team and updates will be provided as soon as we understand the cause.
For additional updates, we ask that you refer to the following article Core Base License error "You cannot access Qlik Sense because you have no access pass"
This weekend students in the MBA course about Predictive Analytics and Data Mining for Executives presented their final project using Qlik Sense! The students were provided a project in the beginning of the semester and were allowed to select their tool of choice. Many decided to use Qlik which was exciting because Qlik employees, David Lyons and Tomilayo Komolafe were able to mentor the students and attend to watch the final presentations. We look forward to working with Virginia Tech at the 2020 Bake Off!
All students are encouraged to join, regardless of their areas of study. Students wishing to improve their analytic and data literacy skills can apply today by visiting qlik.com/academicprogram
QlikTech International AB and its affiliates (collectively, “Qlik”) may from time to time share customer data within its group companies and/or use systems hosted or provided by 3rd parties (collectively, “Subprocessors”) to best provide its Support & Cloud services.
Qlik’s Support services are predominantly performed in the customer region: EMEA – Sweden, Spain; Americas – USA; APAC – Japan, Australia, India.
Qlik’s Cloud systems also utilize 3rd party systems to best ensure a safe and high-quality Cloud service.
The purpose of this document is to inform and keep up-to-date EU/EEA/UK/Swiss Support & Cloud customers of the identities of any Subprocessors for Support services, as per Article 28 of the EU General Data Protection Regulation. Any new Subprocessors will be added to this document within 30 days of appointment.
Any Support data is unlikely to contain personal data given the technical nature of the services, however, in the event personal data is received, it is protected by Qlik’s IT and other security related procedures. In addition, Qlik has in place a network of data protection agreements within its company group and with relevant 3rd party system providers to ensure the lawful and safe transfer, use and protection of personal data.
For questions related to the information in this document, please contact your usual Qlik representative. This document describes Qlik’s services Data Protection/Privacy Law compliance. For Security related questions (e.g. encryption), you can find further information resources at https://help.qlik.com/.
Below is a current list of Subprocessors:
List of Qlik Affiliates which may receive:
List of 3rd party systems/services which may be used:
I have done many inline loads before, but I was not aware of the delimiter option until recently so I thought I would share what I learned in my blog today. When loading data that is typed in the script or added manually via the Data Manager, an inline load is used. Below is an example - it is a simple load script that includes the Inline keyword as well as square brackets to load data directly from the script versus a file or external data source.
Looking at the data in the square brackets, the first line indicates the fields that will be loaded – in this case Name and Age. Each line after that and before the ending square bracket, is a new row of data. Each row is on its own line in the script. This example will load four rows of data with two fields: Name and Age.
By default, the field data is separated by commas in the load script – comma is the default delimiter. I recently ran into an issue where the data I needed to load via the inline load script included commas. For example, assume that Name needed to be loaded with the last name first like this:
This script would load the last name in the Name field and the first name in the Age field and the actual ages would not be loaded at all. This is because there are only two fields listed to be loaded Name and Age so the script ignores the second comma and the age because a third field was not defined (on the line after the open square bracket). There are a few ways to handle this as seen below: 1) “delimiter is” can be used to define a delimiter other than the default comma; 2) double quotes and 3) single quotes. My preference is to use the “delimiter is” option and to use a delimiter that is not part of the data I am loading. All three of these options load the data correctly. If changing the delimiter, be sure to change it on the row with the column names as well as the rows of data.
Using “delimiter is” with the inline load is not required but is useful in certain situations. The delimiter can be any character such as a comma, semi-colon or pipe. The key is to use a character that is not found in the data that is being loaded. Inline can be used to load data as seen in this blog but is can also be added to the script manually via Qlik Sense Data Manager. To learn more about using the Data Manager to load data manually, read my blog titled Manual Entry – Adding data manually in Qlik Sense.
A new addition to our Data Literacy Program, this class is a great way to get your organization started on your journey with Data Literacy, through the structure of a full-day instruction delivered at your site (virtual option also available). Not only will it help your company succeed more with data, this course will empower and help individuals to make smarter data-informed decisions, something that can lead to greater confidence in a career, more credibility, and more.
Read Jordan Morrow's brand new blog to learn more. You can also check out the attached course sheet for more information.
To learn more about our program, visit qlik.com/GetDataLiterate
As I meet with companies through my travels, there are recurring themes to the lack of data and analytical success: a lack of data and analytical strategy tied to organizational goals, skills gaps to making smart, data-informed decisions, and workplace culture. These roadblocks must be remedied for an organization to capitalize and truly realize success with their data and analytical objectives.
To help address this, Qlik is now offering a brand-new class where one of our instructors comes to your location to teach your teams how to create a data literate organization. It is focused on three main subjects: 1.) data literacy and foundational knowledge throughout the data literacy spectrum, 2.) culture and key characteristics that will help organizations weave the DNA of data throughout the enterprise, 3.) how to make smart data-informed decisions. Through this new course, individuals and organizations can truly start to empower the organization’s workforce to make smarter decisions with data, moving the needle for true gains in data and analytical strategy. Let’s look at the 3 sections in more details...
To read the full blog and others written by Jordan Marrow, visit https://blog.qlik.com/fast-track-your-data-literacy-journey
For those of you who are interested in how tickets can be used in Qlik Sense to integrate authentication with identity providers, you should continue reading.
Tickets as a means to give users access to things was used long before the invention of computers. When you go to the cinema, you first need to buy a ticket from a cashier or from the Internet – a ticket that is valid for one movie at a certain time. The ticket is later validated by the person letting you into the correct theatre for the movie for which the ticket is valid.
One benefit of a ticket system is that it is independent of how you get the ticket. The ticket is valid for access to the movie, no matter what.
So how can we use the same concept to gain the same flexibility when we authenticate users in Qlik Sense? We use tickets, but this time the tickets are digital.
In QlikView 11.0 we introduced a concept that called Web Tickets. In Qlik Sense we have developed this idea further and this is now the normal way to make the authentication.
So how does this work in Qlik Sense?
So how do this look in real life if we wanted to integrate with Salesforce?
But for this to be secure, there are two requirements:
Hello Qlik Community,
Here's a quick update to let you know some of the exciting enhancements we made in August and September, as well as a bonus at the end.
1. Labels and Tags Double Filter
We've added a powerful new way to narrow down the posts in a forum or board by label and tag at the same time!
All of our forums and board pages have a labels component in the right rail which can be used as a filter to narrow down the posts list to just the posts with that label. When you click on a label, you'll be taken to a list of all the posts in that location with that label.
Now, we've added a tags component to the Label Page, so that it displays all of the tags that are contained on the posts with the selected label.
Additionally, you can click on a tag from the Label Page, and it will filter again to show just the posts in that location with the selected label and the selected tag, creating a double filter to fine tune the results.
In the example below, I've filtered from New to Qlik Sense > Label: Expression > Tag: Dimensions, which narrowed the results down to one post, which has a solution:
2. Meetups Map Updates
We've update the map on the Meetups page to highlight all of the Qlik Meetup groups around the world.
Clicking on a red dot will display a hovercard with the group name and location, which can be clicked to go directly to that group's page on the Meetup network. This makes it easier than ever to find a Qlik Meetup near you to join in!
Upcoming Meetups listed in the right rail are still denoted on the map with green pins.
3. New Page Banners for Events, Groups, and Blogs
You're used to seeing the blue page banner throughout the community, but now we're adding new, unique page banners to different locations to help distinguish where you are. In place of the global banner on Events, Groups, and Blogs pages, you'll find new, unique banners.
Global Page Banner:
New Events Banner:
New Groups Banner:
New Blogs Banner:
4. Added Events Card to Home Page
5. Fixed Leader Groups Page Listing
We've fixed a bug that was causing the wrong groups to be displayed on the Leader Groups page.
6. Attunity Forum - Coming Soon!
We've added a forum placeholder to let you know that we're in the process of building out a new forum for Attunity products.
While we work on building that out, you can access the legacy Attunity forums at http://forums.attunity.com.
7. Bonus: Qlik Gallery
This week we launched a new page called Qlik Gallery, where you can share your best Qlik apps with the rest of the community. We'll have more info about in our October 2019 Enhancements blog post, but you can check it out now and upload your own!
Happy Autumn everyone!
Jeremy and the Qlik Community Team
On the demo team we end up working with both the Viz API to create and embed native Qlik Sense charts in apps, as well as creating custom components powered by the Qlik Engine using enigma.js, and we do this in Angular, React, and plain html, as we try to demo all of the ways that Qlik can be used. So after my last blog post (Starter project for developing QAP-powered apps with React and enigma.js) we had an idea on the demo team: let's try to unify all of our different custom components and templates. So we've been hard at work accomplishing that.
You may have seen Yianni's last blog post, qdt-components - A Components Library that can be used in simple Html, Angular 5 and React, introducing this effort. The goal is to have the qdt-components library include custom components powered by Qlik Engine, as well as a way to create and embed native Qlik Sense charts. Right now, the qdt-components library contains a few components, but we're not totally ready to start talking about all of them yet, so we're just sticking to the component that allows you to create and embed native Qlik Sense charts by interfacing with the Viz API.
The big addition since Yianni's post is that we've added a React template, so now we have an Angular 5 template, a plain html template, and a React template, all which load the qdt-components, which is pretty cool. This means that the components only need to be built once, but can be used in a project with almost any frontend stack. I say "almost" because in order to use the component that interfaces with the Viz API there's no getting around loading Angular 1.5 and RequireJS into the global namespace, which means they still have the chance to create conflicts. But you can choose not to use the component that interfaces with the Viz API if you don't have a need for native Qlik charts, and it will avoid loading all of the Capability API stuff, but if you choose to use it, you don't have to worry about writing any of the boilerplate you usually do when connecting to the Capability API.
Documentation, examples, and custom components are coming (and oh yea, we plan on using https://picassojs.com/), but that's the update for now. You can check out the qdt-components library and the templates here - Qlik Demo Team · GitHub. And demos of each of the 3 templates below
At the time Dating Apps were all the rage and Qlik had the perfect tool for the job. Qlik's associative engine is ideal for dating apps. Today it would be better with the insight engine in a nice mashup. Our submission for the Connections Mobile App competition is remembered here built in native QlikView Mobile format by our own Kate Perry.
The app did not win, probably as it not "serious" enough, however it did not stop dating-apps from winning the hearts and minds of its users and attracting billion dollar plus (Unicorns) stock market valuations. Tinder for example was valued at $3bn. Who wouldn't have wanted a piece of that?
Note to self : Learn to monetise Fun stuff 🙂
Happy New Year! We’re excited (and hope you are, also) to ring in 2018 with the much-anticipated Dropbox connector now live in Qlik Sense Cloud Business. Our newest connector gives Qlik Sense Cloud Business users more variety and flexibility in how and where they store and refresh data.
And some highlights:
Ready to get started? Use the attached sample data file to test out connectivity with your Dropbox account.
If you missed our November blog post (which you easily may have, because it was accidentally posted to the wrong location), scroll down and read about Amazon RedShift.
For our marketing users in particular, we have two new web connectors for sentiment analysis tools – Repustate and Sentiment140. Now you can have more of your social analytics data in one place, and take a deeper dive into text and content analysis.
Last year was busy as we grew our Qlik Sense Cloud Business community, continuously added new features, and listened to all of your valuable feedback. With that feedback in mind, this year we plan to broaden the capabilities and options in Qlik Sense Cloud to support more use cases and help you find insights faster. Our focus on connectivity will continue, particularly around on-premises connectivity. We’re also working on a wide variety of usability enhancements, new feature additions, and onboarding support and resources - plus the February release features - that we look forward to showing you soon!