This space offers a variety of blogs, all written by Qlik employees. Product and non product related.
By reading the Product Innovation blog, you will learn about what's new across all of the products in our growing Qlik product portfolio.
The Support Updates blog delivers important and useful Qlik Support information about end-of-product support, new service releases, and general support topics.
This blog was created for professors and students using Qlik within academia.
Hear it from your Community Managers! The Community News blog provides updates about the Qlik Community Platform and other news and important announcements.
The Qlik Digest is your essential monthly low-down of the need-to-know product updates, events, and resources from Qlik.
The Qlik Education blog provides information about the latest updates of our courses and programs with the Qlik Education team.
We are happy to announce the next version of our client-managed analytics offering, Qlik Sense August 2023. This version is primarily focused on visualization improvements including a variety of new customization and styling options, and enhancements to navigation and design. Users will also appreciate new support of parquet files, providing storage savings and enhanced performance for large data sets.
In this release, you will find the following new capabilities, many of which are already available in Qlik Cloud today:
Recently, I worked with a Qlik Community member to help them understand the Qlik REST Connector with Qlik Sense and QlikView. At first it appeared simple, but then he soon realized he needed to understand a bit more about how the data came back (the response), what the pagination settings were (pages of data used to retrieve more rows) and finally how to link (join, associate) other attributes that came back from the results of multiple REST API endpoints / resources. We got it all working and the results were pleasing. Needless to say were able to perform text analytics from a barrage of Facebook comments. However, as I finalized all this in my head, I wanted to share what I've learned but in the simplest way possible. So I decided to find a very simple, publicly available RESTful service API in which I can demonstrate my findings easily. The below video presents those findings in a educational and entertaining way using the Star Wars API. Yes, that is correct, I said the Star Wars API. As a bonus, stick to the end of the video to see the Media Box Extension in action.
See this video on YouTube as well. Using the Qlik REST Connector - Pagination and Multiple JSON Schemas - YouTube
Do you know of other simple and fun, publicly available RESTful services? Share them with the Qlik Community in the comments below.
Regards,
Michael Tarallo (@mtarallo) | Twitter
Qlik
Special shout out to: Paul Hallett (@phalt_) | Twitter - for creating an awesome resource http://swapi.co/about that allowed me to easily demonstrate the Qlik Sense REST Connector.
Resources used in this video:
http://swapi.co/api/people/
http://swapi.co/api/species/
Other Resources:
If using Qlik Sense Desktop please copy .qvf file to your C:\Users\<user profile>\Documents\Qlik\Sense\Apps and refresh Qlik Sense Desktop with F5. If using Qlik Sense Enterprise Server please import .qvf into your apps using the QMC - Qlik Management Console.
Disclaimer: Star Wars, the Star Wars logo, all names and pictures of Star Wars characters, vehicles and any other Star Wars related items are registered trademarks and/or copyrights of Lucasfilm Ltd., or their respective trademark and copyright holders.
We are pleased to announce new capacity model pricing for Qlik Analytics. The new pricing model is an extension of the capacity functionality we introduced earlier this year for data integration.
We believe this pricing model aligns with modern customer expectations and will:
Today, we offer three capacity pricing tiers: Standard, Premium, and Enterprise.
You can find additional details on our website Qlik Cloud® Analytics Plans & Pricing
With the Qlik Cloud capacity model, the primary value meter is Data for Analysis or Data Moved, except for Qlik Cloud Analytics Standard where Full Users is the value meter.
See in detail what it means here: Subscription value meters
Additionally, we understand the importance of Qlik Cloud administrators to monitor their tenants' data consumption. Therefore, we are pleased to introduce:
Additional resources:
Thanks for choosing Qlik!
Qlik Global Support
A common situation when loading data into a Qlik document is that the data model contains several dates. For instance, in order data you often have one order date, one required date and one shipped date.
This means that one single order can have multiple dates; in my example one OrderDate, one RequiredDate and several ShippedDates - if the order is split into several shipments:
So, how would you link a master calendar to this?
Well, the question is incorrectly posed. You should not use one single master calendar for this. You should use several. You should create three master calendars.
The reason is that the different dates are indeed different attributes, and you don’t want to treat them as the same date. By creating several master calendars, you will enable your users to make advanced selections like “orders placed in April but delivered in June”. See more on Why You sometimes should Load a Master Table several times.
Your data model will then look like this:
But several different master calendars will not solve all problems. You can for instance not plot ordered amount and shipped amount in the same graph using a common time axis. For this you need a date that can represent all three dates – you need a Canonical Date. This is how you create it:
First you must find a table with a grain fine enough; a table where each record only has one value of each date type associated. In my example this would be the OrderLines table, since a specific order line uniquely defines all three dates. Compare this with the Orders table, where a specific order uniquely defines OrderDate and RequiredDate, but still can have several values in ShippedDate. The Orders table does not have a grain fine enough.
This table should link to a new table – a Date bridge – that lists all possible dates for each key value, i.e. a specific OrderLineID has three different canonical dates associated with it. Finally, you create a master calendar for the canonical date field.
You may need to use ApplyMap() to create this table, e.g. using the following script:
DateBridge:
Load
OrderLineID,
Applymap('OrderID2OrderDate',OrderID,Null()) as CanonicalDate,
'Order' as DateType
Resident OrderLines;
Load
OrderLineID,
Applymap('OrderID2RequiredDate',OrderID,Null()) as CanonicalDate,
'Required' as DateType
Resident OrderLines;
Load
OrderLineID,
ShippedDate as CanonicalDate,
'Shipped' as DateType
Resident OrderLines;
If you now want to make a chart comparing ordered and shipped amounts, all you need to do is to create it using a canonical calendar field as dimension, and two expressions that contain Set Analysis expressions:
Sum( {$<DateType={'Order'}>} Amount )
Sum( {$<DateType={'Shipped'}>} Amount )
The canonical calendar fields are excellent to use as dimensions in charts, but are somewhat confusing when used for selections. For this, the fields from the standard calendars are often better.
Summary:
A good alternative description of the same problem can be found here. Thank you, Rob, for inspiration and good discussions.
Goal Achieved for Hr department:
Use Case:
Target Area :
Requirement :
Solution & Benefits :
Key KPI:
Highlight of this Application:
Hello Qlik NPrinting World!!
Last time I talked about Qlik NPrinting connections, but now we are going to delve into integrating Qlik NPrinting with SAML!
Topics:
What is SAML?
SAML or Security Assertion Markup Language is a form of Single Sign On. It allows the end users to login to the Qlik NPrinting WebConsole and/or NewsStand with the click of a button.
IdP versus SP Initiated SAML:
IdP (Identity Provider) Initiated SAML starts at the Identity Provider URL such as Okta, PingIdentity, ADFS and then redirects the user to the Service Provider URL, Qlik NPrinting.
SP (Service Provider) Initiated SAML starts at the Service Provider URL, Qlik NPrinting, then redirects the user to the IdP for Authentication, and then redirects back to the Service Provider URL.
Requirements:
Limitations:
Configuration:
I worked with the Education Team to help create a "Qlik Fix" video. The video is found here:
It will take you through the configuration steps to integrate Qlik NPrinting with SAML, in the video we are using Okta as our Identity Provider.
To summarize the video:
First enable SAML in Qlik NPrinting:
Click Save
Second setup your Okta Configuration:
Click Finish
On the Sign On screen right click on the Identity Provider Metadata and choose "Save Link As" ensure you save the file with a .xml file extension
Return to the Qlik NPrinting WebConsole - Admin - Settings - SAML Settings
Open the SAML page again by selecting the appropriate name
Browse for the IdP xml Metadata file previously downloaded from the Okta site
Click Save
Navigate back to the Okta Admin page and choose the Assignment tab
Choose the necessary users that need access to the Qlik NPrinting WebConsole
Testing:
Congratulations!! The SAML Authentication should now be setup between Qlik NPrinting WebConsole and Okta. ✔️
A step-by-step guide is found in our Knowledge Article: Qlik NPrinting SAML Authentication with Okta
Are there any other Identity Providers that you would like to see added to our Knowledge? Recently I configured Qlik NPrinting with PingOne PingIdentity. That article is found here: Qlik NPrinting SAML Authentication with PingOne PingIdentity
Please let me know in the comments!
To help answer these questions, we are happy to share with you the capabilities of our Reload Analyzer for Qlik Sense SaaS!
The Reload Analyzer app provides insights on:
(Available sheets)
The Reload Analyzer uses Qlik’s RESTful APIs to fetch all the required data and stores the history in QVD files, allowing for efficient reloads and historical analysis.
A few things to note:
The app as well as the configuration guide are available via GitHub, linked below.
Any issues or enhancement requests should be opened on the Issues page within the app’s GitHub repository.
Be sure to subscribe to the Qlik Support Updates Blog by clicking the green Subscribe button to stay up-to-date with the latest Qlik Support announcements. Please give this post a like if you found it helpful!
Kind regards,
Qlik Digital Support Team
Additional Resources:
Our other monitoring apps for Qlik Cloud can be found below.
企業のビジネス活動において、データはこれまで以上に必要不可欠な資産となっています。増え続けるデータを管理・統合・分析し、データでアクションを起こす必要性が増している現在、成功している企業はどのようなデータ戦略を実行しているのか?
本 Web セミナーシリーズでは、Qlik でデータからアクションを起こすデータ主導のビジネスで成功しているお客様より、課題から導入の経緯、デモンストレーション、活用例などをご紹介します。
本田技研工業株式会社では、全社共通データ分析ツールとして Qlik sense を導入し 7,000 超のユーザーが日々利用しています。 本セッションでは、データ駆動型のビジネスを実行するための体制と、その考えに基づき実践した Qlik データソンでの取り組み事例を紹介いたします。 第 3 回 Qlik データソンにおいては、ユーザー部門で最優秀賞を受賞。5 時間という限られた時間の中でいかにして成果を出したのか、ビジネス課題を解決するためのデータ分析の取り組みと Qlik の活用についてお話しします。
The straight table, included in the Visualization bundle, has all the table properties that we are used to as well as many new features. These new features make it easier for developers to create a straight table and it gives users the ability to customize straight tables in the apps they view. The straight table is ideal when you want to provide detailed data – the raw data. While you do not want to have too many columns (ten or less columns are ideal for the best performance), a straight table can have many columns (dimensions and measures).
As previously mentioned, the straight table can be added to a sheet from the Qlik Visualization bundle. This means developers will need to open the advanced options to add the straight table to their sheet(s) and make edits. Once the straight table is added to a sheet, developers can add columns – either fields and master items or custom expressions. One of the new features that developers can take advantage of to build tables quickly is the ability to add more than one dimension and/or measure at once. Simply select the dimensions and measures you would like to add to the table and then click the Add button.
Once columns are added to the table, they can be dragged as needed to the desired position/order. Developers also can add alternate columns to the straight table. These columns can be dimensions and/or measures. These alternates columns will be available to users to customize the straight table if chart exploration is enabled. This is a great new feature because the user does not need edit permissions to modify the straight table. Users can add and/or remove columns based on their analysis. Being able to add columns as needed also improves performance since the straight table does not need to display all the columns, all the time. Loading the straight table with the minimum columns needed will decrease the load time.
Chart exploration allows users, who are in analysis mode, to add and remove columns from the straight table they are viewing by checking or unchecking them in the Chart exploration panel (see image below). Any users viewing the sheet can customize the straight table. Users cannot see layout changes made by other users using the app, unless they opt to share the visualization or create a public bookmark with the layout saved.
Another new feature for developers is the ability to set the column width. By default, the column width is set to Auto, but developers can set it to Fix to content, Pixels or Percentage. Pagination is another new feature that can be enabled in a Straight table. With pagination, a specified number of rows are displayed at once and the user can navigate through the pages using arrows or selecting the page.
Many of the properties for the straight table are familiar but the new ones are moving the straight table to a new level. Learn everything you need to know about the straight table in Qlik Help and add one to your next app. Also check out the SaaS in 60 video for a quick video overview:
Thanks,
Jennell
Starting from the week of August 14th 2023, Qlik Cloud Analytics will no longer be able to utilize non-supported Microsoft SQL data sources. This affects Microsoft SQL Server 2012 and earlier.
Microsoft SQL Server 2012 and earlier are not supported by Microsoft (see SQL Server lifecycle dates). If you are unclear which version of SQL Server you have, use one of the methods described in this Microsoft article.
Upcoming Changes
Qlik Cloud Analytics is performing a required security update in August 2023, resulting in no access to Microsoft SQL Server 2012 or earlier. This update will also result in no support for TLS version 1.1 and earlier as well as any deprecated cryptographic functions.
Additional Information
While client-managed and standalone web connectors are not directly affected by this change, they do not support outdated versions of Microsoft SQL Server, such as MS SQL 2012. See Supported Microsoft SQL Server versions.
For additional information, see Outdated, out of support versions of Microsoft SQL Server and Qlik Cloud Analytics.
Thanks for choosing Qlik!
Qlik Global Support
Qlik Sense Map charts are used to geographically display data related to countries, cities, states, regions, or particular geolocations (etc…). Maps offer different ways to present your data by first setting a base layer, then adding multiple layers to the map which are specific locations highlighted in multiple ways including Area, Points, Lines, Density, boundaries etc..
You can add as many layers as you want. These layers are comprised of dimensions and measures that allow to efficiently present geographical distribution of values related to locations in order to display a data story.
Using different base maps can enhance the way data is displayed and aid in analysis. You can choose from:
When including multiple layers in map chart, it might become hard to interpret data. In that case, you can address this by controlling at what zoom levels different layers appear or have layers that appear only if other values in a drill-down dimensions are selected. This allows to create multiple levels of detail as you make selections and zoom in and out or locations of interest on the map.
Let’s create a map that relies on Zoom to reveal different layers.
The result:
Let’s create a map that uses a drill-down dimension to display layers based on selection. Keep in mind that Drill-down dimensions should have the fields in order of highest geographical are to smallest geographical area.
The result:
Tip:
If you load data and it appears incorrect like below:
Head to Location, switch off Scope for location from Auto to Custom.
Change Location Type to “Administrative Area (Level 1)” in our case. Then, change Country to your location, in our example it’s ‘US’
Let’s create a map with multiple background layers using a TMS and two WMS.
Important:
Keep in mind that when using URLs for TMS and WMS formats for background layers, these URLs that contain resource requests to external resources must have its origins allowlisted in the Content Security Policy, else the resource will not be loaded. WMS resources must have both image-src and connect-src directives allowlisted. More Info here.
The Result:
The QVFs for all three advanced examples can be found below. You can load them to your Qlik Cloud tenant, investigate the chart settings, and tweak the configurations to practice these concepts.