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 10 SR6 is now generally available to customers and partners. The software and release notes can be found on the download site (http://global.qlik.com/download). This release also includes the solution to the security issue that was addressed in the QlikView 11 SR2 update, details of which can be referenced here http://community.qlik.com/blogs/technicalbulletin/2012/11/29/qlikview-11-sr2-update
Please report any issues to the QlikTech Support group through the normal channels
The Products Team
Our current month names come from the Roman calendar. The original Roman calendar had ten months: Martius, Aprilis, Maius, Junius, Quintillis, Sextilis, September, October, November and December. The first four months were named after gods: Mars, Venus (Aphrodite in Greek and Apre in Etruscan), Maia and Juno. The origin of Aprilis is debated, but we know that the month was sacred to Venus because the Festum Veneris et Fortunae Virilis was held on its first day. The last six months are based on the latin words for five, six, seven, etc.
Each year started in March and ended in December, 304 days later. It was then followed by a period of festival between the years.
But the calendar was soon changed by the king Numa Pompilius around 700 BC, who added Januarius (after the god Janus) and Februarius (after the purification festival Februa). He also moved the beginning of the year to Januarius.
However, the year was still too short - only 355 days - so the Pontifices occasionally had to add an extra month to keep the calendar in sync with the seasons. This decision was political and was sometimes done just to extend the term of a particular public official. Or it wasn’t done at all, if the official was an opponent.
By the 1st century BC, the calendar had become hopelessly confused, so in 46 BC, Julius Caesar initiated a reform that resulted in the establishment of a new calendar, the Julian, which was a vast improvement: Leap years were introduced and the year in the Julian calendar was on the average 365.25 days, so no extra intercalary month was needed. After Julius’ death, the month of Quintilis was renamed Julius in his honor, hence July.
Julius Caesar was succeeded by Augustus, and after his death the senate renamed Sextilis after him. At the same time, the senate also suggested that September be renamed after the reigning Caesar Tiberius. But Tiberius refused with the words: “And what will you do if there be thirteen Caesars?”
Today most countries use the Gregorian calendar, which is based on the Julian and still has the Roman month names from 2000 years ago.
In QlikView and in Qlik Sense, the abbreviated month names are defined in the environment variable MonthNames.
Set MonthNames = 'Jan;Feb;Mar;Apr;May;Jun;Jul;Aug;Sep;Oct;Nov;Dec';
This variable is used by several functions, e.g. Month() and Date(). The format code ‘MMM’ is always mapped against the content of this variable.
You can also create an environment variable for the long month names, corresponding to the format code ‘MMMM’:
Set LongMonthNames =
If you have these variables, you can use the long format codes not only for formatting of date fields, but also for interpretation of fields, e.g.
Date(MonthStart(Date),'MMMM YYYY') as YearMonth, // Creates and formats YearMonth
Date#(Date,'MMMM DD, YYYY') as Date, // Interprets the Date='October 9, 2012' as a date
Dual(MonthTxt, Month(Date#(MonthTxt,'MMM'))) as Month, // Interprets the MonthTxt='Oct' as a month
Bottom line: You should define fields for months in your master calendar and add an environment variable for long month names.
Further reading related to this topic:
QlikCommunity offers relevant content for our viewers including a variety of Blogs which are updated frequently. We invite you to visit our different blogs and subscribe to the ones that interest you the most.
Navigating to our Blogs
You can access recent blog posts from the feed on the home page, or select Blog Posts from the Browse menu to see all the blogs.
Once you are on the main Blog page you can select the blog you want to visit from the right hand side of the page.
When you find a Blog which is interesting you may subscribe to it so that you receive a notification when a new post is published.
2. Subscribe via the Actions Menu
You may choose to subscribe to it in 2 different ways:
3. Select the Blog feed you want to subscribe to
The system will open your RSS feed tool and follow the steps to subscribe as set by your particular RSS reader tool.
(I use Chrome so this screen shot shows my view)
Your subscription should now be enabled.
QlikView 11 SR2 Update 2 was issued today. This update includes a resolution to a security issue discovered in the product. More details on this fix can be found in the release notes. The specific vulnerability relates to multiple users simultaneously logging in to a document while it is being reloaded in memory, and the vulnerability exists only if that document has dynamic section access reduction with a numeric reduction field. The steps to reproduce this vulnerability are therefore complex. As with any security patch we recommend all customers to take this update release. If you are using Section Access, this release should be regarded as a critical upgrade.
This update will also be part of the QlikView 10 SR6 release, due around the end of the year.
We are pleased to announce that Version 11 SR2 Update 2 - build 11.00.11440 is now available. This Update replaces Update 1 (11.00.11426). Unfortunately Update 1 contained two degrades which affected users of Windows XP and Windows Server 2008 (not Server 2008 R2).
We regret the inconvenience caused. You can download the installation files for Update 2 from http://www.qlik.com/download.
Please see attached release notes for further information.
Global Support Team
Back in 2001, with the release of the now cult-classic film Donnie Darko, there was a website that came out to accompany the film. The site was (and is) as cryptic and vague as the movie. There is this quasi linear path through the site but at the same time no clearly delineated objective - you experience the site and you do so just for the sake of experiencing it. It doesn't need to tell you what theaters the movie was being released in, or when it was being released because you could get that information other places. This site was for enthusiasts, for die-hard fans. It was something to play with that added to the richness of the film by extending the experience of the film.
Now contrast this with a site that sells movie tickets. There is a clear objective. You use it to buy tickets online to save you from having to buy tickets in person. I go to these sites with a purpose, I complete my task, I leave. It's a tool to do a job.
The balance between creating a tool vs. creating a toy isn't always this clear. You want to create a pleasant experience, even something cool, but if the primary objective is to enable people to complete a task then you should focus on building a useful tool. Help your users do the thing they came here to do. In the case of QlikView this means building applications that focus on the user's needs, apps that clearly show the data, that help users explore their data and find new insights.
I've seen more than a few applications where people, with the best intentions, tried to create a fun environment but ended up adding too many pieces of unnecessary visual "flare." When considering a background, a chart, an animated logo, or a photograph you need to ask yourself: "is this going to help people use this application?" If the answer is no, then perhaps it is best left out. There are plenty of well designed applications that take a very minimalistic approach to design. The application should be well designed, but well designed this isn't synonymous with having a trendy aesthetic. You don't need to cram in all the design tricks you know.
Real design solves problems and the application you are building should be a tool to help people solve problems and complete tasks.
QlikView Connector for use with SAP Netweaver Version 5.7 SR1 is Released and available for customers and partners
Key enhancements include:
- Modified logon dialog requiring test connection prior to creating connection string within the script.
- Transport version check with custom error messages to prevent mismatch between windows and SAP installation files.
- Drop down on the SAP Extractor screen within SAP to facilitate searching for activated extractors.
- Addition of field descriptions to the generated scripts.
- Ability to resend single idocs
- Variable selection parameter improvement on selection.
- Configuration parameter for BatchJobName added to connection string to allow modification of the default job name /QTQVC/READ_DATA.
- Configuration parameter for RemoveThousandSeparator added to connection string
- Configuration parameter for ReplaceNullvalue added to connection string
You can find the software on our Download site by navigating to the "Connector" tab
The Products team
Have you ever received a design and wonder how you were going to replicate it in QlikView? Well, I came across this challenge when creating the Social Media Data Analysis demo. Our UI designer designed a chart that that looked something like the image below:
Now at first glance, you may consider designing this in QlikView using individual text objects for the labels and expressions. That was my first thought but then I realized that there would be a lot of text objects to maintain when changes were made to the expressions. So I tried to recreate this chart using a pivot table. While it was easy to add the dimension and the three expressions, it was a little more difficult to add the perks like a background color for the highest value but only for selected companies. For example, in the chart below, Company A, Company C and Company D are selected so I only want to see the highest values based on those selections.
There were also challenges like the dimension label and background color or the fact that the background color for Company A Followers extended to the left to the label. It was little things like this that made this chart a challenge.
But with the use of set analysis, background colors, text color and some carefully placed text objects, I was able to create a visualization that was not as pixel perfect as the Photoshop design but close to it using the basic features and functionality of QlikView. Read more about how I created this chart in this technical brief.
The use of the seven-day week is ancient. Signs are found in the old Greek, Indian, Persian, Babylonian, Jewish, Akkadian and Sumerian cultures. Most likely it was invented by the Sumerians around 4500 years ago.
The Sumerians named the week days after the celestial bodies: The sun, the moon and the five known planets. Since the planets had names after gods, some days were thus also named after gods. These names were then translated into Babylonian, then into ancient Greek. In both translations the corresponding local gods were used.
Set DayNames='Nanna;Gugalanna;Enki;Enlil;Inanna;Ninurta;Utu'; // Sumerian
Set DayNames='Sin;Nergal;Nabû;Marduk;Ishtar;Ninurta;Shamash'; // Babylonian
Set DayNames='Σελήνης;Ἄρεως;Ἑρμοῦ;Διός;Ἀφροδίτης;Κρόνου; Ἡλίου'; // Greek
Set DayNames='Moon;Ares;Hermes;Zeus;Aphrodite;Cronos;Sun'; // Greek
The Romans, however, did not initially use a seven-day week. But a decision by Emperor Constantine in AD 321 eventually established the seven-day week also for the Roman Empire. Once again the names of the gods were translated to their local counterparts:
Set DayNames='Lunae;Martis;Mercurii;Iovis;Veneris;Saturni;Solis'; // Latin
Hence, the Latin names of the gods were mostly translations of the Greek names, which in turn were translations of the Babylonian names, which go back to the Sumerians. The Latin names can still be recognized in most Romanic languages, e.g. in French:
Set DayNames='Lundi;Mardi;Mercredi;Jeudi;Vendredi;Samedi;Dimanche'; // French
The Germanic tribes in northern Europe started to use the seven-day week long before they converted to Christianity, so the day names, except sun day and moon day, have the names of the old Germanic gods: Tyr/Tiw, Odin/Wotan, Thor/Donar and Freyja/Frige.
But for Saturday, the day was not translated. It is still “Saturn’s” day in e.g. both Dutch and English. And in all Nordic languages it is the “Washing day”. Because that is what you were supposed to do on Saturdays.
In QlikView, you can customize the day names by changing the variable DayNames as I have done above. These values will then be used by the WeekDay() function. Alternatively, you can create a new variable, e.g. vDays, and use this in the following field definition:
Dual(Subfield('$(vDays)',';',WeekDay(Date)+1),WeekDay(Date)) as WeekDay
But on which weekday does the week start? And which week is the first week of the year? The ISO 8601 defines these things clearly:
This means that if Jan 1st is a Friday, then week no 1 starts Monday Jan 4th, and the first three days of the year belong to the last week of previous year. It also means that if Jan 1st is a Thursday, week 1 starts Dec 29th. The ISO 8601 is used in many countries, among them most European ones.
But in North America and in the Middle East, different conventions are used. Often Sunday is considered the first day of the week. And Jan 1st is in some countries always part of week 1. As a consequence, the first and last week of the year are often fractional.
The QlikView week functions all use ISO 8601. If you want to define these entities in a different way, do the following: Introduce two variables that define your new week system:
Set vFirstWeekdayOfWeek = 6 ; // 0=Mon, 1=Tue, 2=Wed, ... , 6=Sun. (For the U.S. = 6)
Set vMinDaysInWeek = 1; // Minimal number of days in week no 1. (For the U.S. = 1)
Then you can define your week fields as:
Dual(WeekDay(Date),Mod(WeekDay(Date-$(vFirstWeekdayOfWeek)),7)) as WeekDay,
Ceil((Date-FirstDateOfWeekOne+1)/7) as WeekNumber,
Date(WeekStart(Date-$(vFirstWeekdayOfWeek))+$(vFirstWeekdayOfWeek)) as WeekStart;
+$(vFirstWeekdayOfWeek)) as FirstDateOfWeekOne, …
Bottom line: Define fields for week day and week number in your master calendar. And don't hesitate to change the environment variables if you want long day names or different day names.
Further reading related to this topic:
We are excited to announce the availability of the QlikView Direct Discovery beta.
The beta is open to all QlikView customers and partners.
Direct Discovery capability enables you to work with massive amounts of data from Big Data sources using QlikView’s intuitive associative analysis experience.
We have created a beta community, where you can discover more about this new QlikView capability, report bugs, start open discussions and ask questions. Your participation and opinions are of crucial importance to us to ensure we continue developing and deploying the highest quality products possible.
The beta will run until November 18th 2012. We kindly ask you to provide your feedback until then.
We look forward to hearing from you
See you in the beta community.
The QlikView Product and R&D team
One of the common business requirements when analyzing the data is limiting the dimension values on a chart. For instance, limiting the chart to the top 10 sales people, or showing only the products that make up 80% of sales. QlikView 11 dimension limits functionality enables the business users to easily create these logics on the charts.
This functionality provides consistency across QlikView charts and more importantly better performance. Prior to QlikView 11, some charts in QlikView could display totals at the expression level, some can limit the number of dimension values to display and some can display an ‘OTHERS’ dimension value to catch those values omitted by the limits. With QlikView 11 dimension limits feature, these functionalities are consistent across chart types. Also, the conditions that are used on the dimension limits are calculated at the engine level, providing better performance and calculation time.
The functionality offers four main options:
Each option has a separate set of applications and can be used in different permutations.
QlikView 11 dimension limits functionality makes it easier for the business users to customize the QlikView apps based on their own analysis needs with just a few clicks!
QlikView Direct Discovery Beta Registration is Open
We will be launching beta for our upcoming QlikView Direct Discovery for direct access to big data sources within QlikView apps in November 2012. The beta will be open to all customers and partners.
Customers and partners can start enrolling in the beta program. To take part in it just send mail to firstname.lastname@example.org.
As part of QlikView’s Big Data Discovery strategy, Direct Discovery can link data already loaded in-memory with big data sources for rapid visual analysis. With this hybrid model for comprehensive analysis, there is no need to choose between direct access to big data or pre-loading data in-memory. QlikView Direct Discovery will be part of the QlikView Version 11 upgrade available in December 2012 at no additional cost.
We hope to see you on the beta list!
The Products Team on behalf of
Irena Calovska - Beta Program Coordinator
Hello Qlik Community.
QlikView Expressor 3.8 is now available on http://download.qlik.com/.
Great job by the products team!
A highlight of this release is its new parameter and configuration manager. This will allow a QlikView Expressor developer to configure parameters that can use substitutable values individually or saved as a set for configuring operator properties at run-time, simplifying the reuse of QlikView Expressor Dataflows in different environments. In addition - support for the QlikView licensing model, improvements to the schema wizards and enhancements to data source connectivity have been added. Read on to learn more.
This release includes the following new features and enhancements:
New - Parameterization & Configuration
This is a must have core capability that simplifies the reuse of QlikView Expressor applications in different environments. It is now possible to manage and use sets of configuration values as needed to support the movement of a QlikView Expressor application through development, test, and production.
Click to enlarge
Figure 1. QlikView Expressor Parameter Manager and Parameter setting dialogs (example shown: database connection)
For example, in an IT environment that has a different project lifecycle stage for DEV, TEST, and PROD, it’s now easy to create and use three sets of database connection properties (one each for DEV, TEST, and PROD). When the QlikView Expressor application is deployed in the TEST environment, it can easily be configured to run with the TEST configuration values. Configurations are managed, shared, and reused between users and projects just like all other QlikView Expressor metadata artifacts. Resolved parameters are also available through Datascript at runtime.
New - Licensing model
The old Expressor licensing implementation has been replaced with the familiar QlikView licensing model.
Figure 2. New Licensing model dialog in QlikView Expressor Desktop
Enhanced - QlikView Expressor Connector
Stability and quality of the QlikView Expressor Connector has been improved, licensing restrictions are now enforced, and changes to support the 1.0 Beta release of the Governance Dashboard have been implemented. The QlikView Expressor Connector also supports the above method parameterization. When using the QlikView Expressor Connector as a data source in QlikView you can override the parameters that were defined in the Dataflow. Allowing the QlikView developer to substitute values for named parameters. This eliminates the need to change the Dataflow in regard to any parameter supported by the Named Parameters feature:
Click to enlarge
Figure 3. Override QlikView Expressor Dataflow property parameters in the QlikView Expressor Connector
Enhanced - QlikView and Excel extensions
Figure 4. QlikView schema metadata data type update
Figure 5. Excel Schema Wizard data preview
Enhanced - Database connectivity
Senior Product Marketing Manager
We are really proud to announce that we’ve shipped QlikView 11 to the world! This is our most social, mobile and enterprise-ready version ever, and we’ve collected this list of eleven resources to help you get the most out of this new release:
I hope that you find these resources helpful, and you will soon be well on your way to working and creating great Business Discovery apps in QlikView 11! If you have created any resources around QlikView 11 (blog posts, videos, etc.), please leave them in the comments section for others to see!
This is a reminder that support for version 9 ends on 31 October 2012.
For customers who wish to extend support for version 9, please see Extended Update Support information in the QlikView Support brochure http://www.qlik.com/us/~/media/Files/resource-library/global-us/direct/datasheets/DS-QlikView-Support-Services-Brochure-EN.ashx
Extended Update Support is a paid for support extension, the cost of which can be found in the pricing page on our web site : http://www.qlik.com/us/explore/pricing.
Version 11 Service Release 2 is now available on our download site.
If I say the word “Dashboard”, most readers probably think of a software tool that gives an overview of enterprise health, rather than of a control panel in front of the driver in a vehicle. One is in a computer, and the other is in a car, but they should play the same role; it should alert you when something is wrong. So where do we start when creating a dashboard for business users?
I follow a D-A-R concept: dashboard-analysis-report. The first QlikView tab, the dashboard, tells users what is good or bad. It’s the “what” sheet. The next batch of tabs is for analysis and has graphs and tables which tell users “how” or “why” things are good or bad. The last part, the report sheet, has more detailed information such as invoice details, order details, employees’ shifts and so on where users can identify the exact action item to act on. So when creating a dashboard, it’s important to highlight the “what” in it.
The first step is to identify the key metrics. The fewer the better. Don’t place 50 KPI’s to try to characterize the entire company in a dashboard, but rather the major ones that matter the most. Pick metrics that change every day if the dashboard is to be utilized daily.
Secondly, make sure all KPI’s have a comparison. Human beings are trained to compare everything 24/7. If your sales figure is 3 million dollars, then so what? Is it better than yesterday’s number? You need to place a comparison number to indicate whether it is better or worse.
Next, don’t use the color green when something is good. If you have 4 KPI’s (key performance indicators) and two of them are green and the other two are red, then people take it as 50% good, not 50% bad. You want users to focus on the ‘bad’ part so they can act on it. Only color-code what is bad, that is, red.
Compare with a dashboard in a car. It does not alert you when something is doing well, but it is designed to alert you on the bad things. Think about the fuel light. It’s not lit in green when your car has enough fuel. Instead it alerts you when fuel is critically low. Then it comes on in red and you notice it right away. It grabs your attention and personally I even get nervous when I see it.
Think about a usage of gauges. A big number with a small red color indicator will do a better job to alert users than a round gauge with both green and red in it.
Bottom line: When designing a dashboard, make sure to keep it as simple as possible. When a user looks at it for 10 seconds and looks away, she or he should remember what was bad. Otherwise, it is not playing its fundamental role and is just pretty to look at.
Executive Dashboard on demo.qlik.com.
Here is a technical brief on this topic.
We are pleased to confirm that Version 11 Service Release 2 is now available on http://www.qlik.com/download.
Service Release 2 contains the new QlikView Offline Capability [see page 20 in the release notes], 6 Design Corrections and over 200 bug fixes.
Please make sure you read the release notes before upgrading to this Service Release. Thank you to all the customers and partners who participated in beta testing Service Release 2.
Global Support Team
We know how important it is to gather and share information via social networks. We recently launched a nifty new social media toolbar on the QlikView.com website AND QlikCommunity.
Business Discovery Blog- See the most recent blog posts
Facebook- See our most recent postings, Share and Like content with your Facebook friends
Twitter- Follow us or retweet from the QlikView Twitter channel
Share- Share the page you’re visiting with your social media contacts
Forward- Share the page you’re visiting with notes via email
Now you can quickly and easily access our different social media channels or share pages with your friends using this tool from the left hand side of any page in QlikCommunity. We’re always working to innovate and hope you like it .