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 11.20 SR2 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).
In addition to addressing over 150 bugs, this release adds support for 64-bit versions of Windows 8 and Windows Server 2012. Internet Explorer 10 is now also supported both on Windows 7 and Windows 8 (except for touch usage).
In addition SQL Server 2012 and Good Browser from Good Technology are now supported.
Please report any issues to the QlikTech Support group through the normal channels
The Products Team
In a presentation, or a seminar or just a conversation, the speaker starts presenting the topic by introducing the title of the topic, then gives a brief overview, the background and then gently flows into talking about the details of the topic and concludes with the summary or an inference.
Similarly, when writing an article, one first starts with an abstract, an introduction, then writes the details of the topic in the body and ends by writing a summary or a conclusion.
Order and organization of information from a reference point to the last detail, in sequence, is the most crucial part of effective and seamless communication and storytelling.
Design, like writing, or a verbal presentation, or even a casual conversation is a medium of communication and a channel for storytelling. It follows the same principles of hierarchy and order as in any method of communication. Only when information is organized in a good hierarchical manner, the story is told most effectively.
Most people are visual thinkers, chances of people understanding a set of images and text put together in a grid with no starting or an end point are very slim, instead, going through and comprehending information which is ordered in a top to bottom approach is much more meaningful.
For instance, the design of a newspaper is a classic example of using hierarchy in the most effective way to help people read highlights and pick information they want to read. Hierarchical patterns in design can not only aid comprehension but also enable quick scanning of information, guide the user through the story and improve usability.
As time becomes an increasingly valuable commodity, grabbing the user’s attention and retaining it has become the most important and the most challenging thing today. Designing information in a way that calls for the user’s attention and retains it is the key to a successful communication strategy and Hierarchy forms one of the most important ingredients for effective communication.
In a QlikView application the D-A-R concept (Dashboard, analysis, report) is a great method to provide contextual hierarchy where the content is presented in a top down approach. This makes it easier for the user to grasp the data from start to finish and also enables them to pick out information that they intends to drill down to and analyze.
However basic and overemphasized these principles may seem, the fact is that they always seem to work and give rise to good user experience. Research and usability tests prove that when a design layout adheres to the basic principles of design, the design becomes more user-friendly, simple and obvious. Hierarchy is one of the most important principles of basic design and should be applied to all designs from simple to complex.
A technical brief can be found here which expands more on this topic.
We sometimes suffer from trying to show as much information as possible in QlikView. In order for us to categorize the information so the users can consume it more easily and smoothly, the first option you may consider is using tabs.
Tabs are a great way to categorize the information for users; however, if you abuse the tab system in QlikView, users may get confused or miss some important information that is available for them. This is why.
• When there are too many tabs, then QlikView wraps the tabs and creates multiple rows of tabs in QlikView Desktop.
• The point above is a different usability in AJAX client when many tabs exist. QlikView creates buttons to navigate the rest of the tabs that are hidden, just like MS Excel. As you can imagine, this can be a risk of users missing some information.
Have you seen an application like this? Well, I have. Yes, in a real life use case.
In this extreme case, rows of tabs can be as many as the example above. This is an example with 1024x768 screen resolution. As you can see, we are losing the real estate for information display for the tabs. It is about 1/3 of the entire real state for tabs.
In order to avoid this tab nightmare, you have a few options to overcome this situation. First, think about the hierarchy of your information categories. Then, consider using 1) a container object, 2) sub-tabular system, 3) a multi-box or 4) combination of these options.
This is one example of using the Option2: sub tabular-system.
If you are curious to know more about this topic, you can see the tech brief here. More example snapshots and how each option works are documented in detail.
I hope you have a better understanding on how to deal with many tabs in QlikView.
NOTE: Files that work with QlikView Personal Edition will have the following in their description:
***This application is Personal Edition compatible. ***
If you do not see this text, then the file is NOT compatible and will consume one of your four recovery attempts should you try to use it. We are adding PE Compatible files on a rolling basis.
One of the best ways to learn about the capabilities of QlikView is through tutorial files, which provide helpful hints like expression examples, code blocks and design advice. In addition to the QlikView tutorials installed with the software, the Share QlikViews section of QlikCommunity hosts over 100 sample QlikView applications that have helped our members learn about new, different and even fun uses of QlikView.
With QlikTech's recent release of QlikView 9 and the advent of the Personal Edition, there is now a new crop of QlikView users joining our community: developers that have an unlimited amount of time to learn, test and create QlikView applications. The one limitation of QlikView Personal Edition is the ability to open QlikView files created by others, which until now prevented these users from downloading and learning from the files in the Share QlikViews section.
Starting today, we are going to enable QlikView Personal Edition users to download and use files uploaded by our Community to enhance their QlikView skills and knowledge. This will change a couple of processes on the site, but the day-to-day impact will be minimal. These changes include:
We greatly appreciate all of the uploads to the Share QlikViews section over the past few months; our library of files now exceeds 100 files that have been downloaded more than 20,000 times! In order to keep the section as useful and easy-to-navigate as possible, we are going to establish a couple of guidelines for uploads to the Share QlikViews section:
- Safe - virus-free, no unsafe macros, functioning load script and data model
- Educational - demonstrates a difficult or complex QlikView functionality (Set Analysis, Google Maps, load script tips and tricks)
- Useful - serves as a functional QlikView application for day-to-day, personal use (bank account application, contact manager)
- Fun - using public datasets to create cool QlikView applications (World Cup, Tour de France, World of Warcraft)
These guidelines are not exhaustive; each file will be reviewed, and if there is any problem, we will contact the author of the file to get it resolved.
All members, including Personal Edition users, can upload apps to the site, and they will be reviewed per the preceding guidelines. Once approved, we will apply a Universal License Key to the file that will allow it to work with Personal Edition.
We will begin adding the key to popular files already in the Share QlikViews section, and will denote the files by adding a "Personal Edition Compatible" tag and headline to each file's description. This process will happen over the next several weeks.
Thank you again to all of our members that have contributed files up to this point, and we hope that the new Personal Edition audience will encourage more of you to participate!
Usability engineers & researchers are crucial parts of User Experience. While not as "glamorous" as designers they bring evidence to the world of design. Through observation of heuristic tests they offer empirical evidence that a design is working, failing, what users like, what users aren't finding, what users are doing that they don't even realize they are doing it, etc. Usability is the closest thing design has to being a science.
The attached technical paper goes through a variety of topics with usability in mind and makes recommendations. It links out to studies and research already done supporting best practices.
The basic findings and recommendations in this document are that:
• People don’t read everything online, they skim
• Paragraph width impacts comprehension
• Scrolling is good
• Monitor Resolution: design for 1024x768
• Ipads: design for 1024x768 and allow scrolling
• Icons don’t necessarily help usability
• Filters should be on the left
When using QlikView, sometimes we are faced with challenges such as how do we transform an Excel spreadsheet that looks like the image below into a trial balance chart that allows us to see the monthly activity for each company and account.
Well using various functions and features of QlikView such as:
• CrossTable Load of Excel spreadsheet
• IsNull() function
• RowNo() function
• Peek() function
• Date functions
• Preceding load
We can create a trial balance sheet that looks like this:
Creating this chart involves loading the Excel spreadsheet into QlikView in a format that works best for us using a CrossTable load. After sorting this data by Company Number, Account Number and Month Year, we are ready to create the Opening and Closing fields that we will need for the trial balance chart. Using the RowNo() and Peek() functions, we are able to create the opening and closing balance fields for each account number on a monthly basis allowing the user to see what the activity was like during any given month. Here is a snippet of what that script looks like:
You can view the step by step details of how the trial balance chart was created in this technical brief.
We are preparing QlikCommunity for a platform version upgrade which will include a number of enhancements which include:
We are targeting mid June for our upgrade and are currently working on some content clean up and restructuring. Here are some changes you can expect to see:
QlikView Applications – Removal of the QlikView Application Content type. All QlikView Applications will be converted by their owners into Document format with specific naming and tagging.
*If you own a QV Application we are posting detailed instructions on how to properly convert it to the new format and will also be available to assist you.
Forum Categories and Tags – We are currently evaluating categories and tags used in forums to see what updates are needed. Some categories may potentially become their own forums based off of activity and content type. Tags are always a challenge and during the upgrade we will try to standardize similar tags as much as possible to improve the tag clouds and search experience.
Resource Library - Documents will be moved into a new Resource Library area so you can more easily search on and find How-to Videos, Technical Guides, QlikView Applications, etc. Expect to also see additional standardization of categorization, naming and tagging for existing and new resources.
Broken link clean up - We always look for broken links in the community. As discussions and resources both inside and outside QlikCommunity move or are retired links become obsolete- if you see a broken link please post it here or email me at email@example.com so we can find a valid link to replace it or delete the reference.
If you have questions please feel free to share them!
QlikCommunity Management Team
QlikView 11 SR2 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)
QV11 SR2 contains one very significant new capability (QlikView Offline Capability), 6 ‘Design Corrections’ and a series of bug fixes.
QlikView Offline Capability
With the release of QlikView 11 SR2, QlikView now supports offline mobile functionality. The new QlikView for iOS app allows for taking data and insights with you on the road when no connection exists. Users can now access QlikView documents on their iPad in ‘offline’ mode (i.e. not connected to the QlikView Server). This functionality requires the installation of the QlikView Offline Service on the server side, which is available in a separate installation file from the product download page. The QlikView for iOS app is also needed, to be available shortly on the Apple App store. The iOS app is being released in conjunction with the release of QlikView 11 SR2.
There is a lot more information available about this new capability, as well as its limitations of use, available in the Release Notes for QlikView11 SR2 available on the download site at http://global.qlik.com/download
Please report any issues to the QlikTech Support group through the normal channels
The Products Team
Hello QlikView users,
We are pleased to announce that QlikView Version 11.20 Service Release 2 is now available for download and install on www.qlik.com/download. In addition to normal bug fixes, SR2 adds support for Internet Explorer 10, 64BIT Windows 8* and Windows Server 2012. Please see the release notes for details on bugs fixed and software changes.
* touch functionality in Windows 8 is not supported.
As blogged about earlier, please remember that QlikView 10 End of Support is 30 November 2013.
QlikView Version 11.2 Service Release 2 Beta is now available to customers and partners.
This release adds support for 64-bit versions of Windows 8 and Windows Server 2012. Internet Explorer 10 is now also supported both on Windows 7 and Windows 8 (except for touch usage).
In addition SQL Server 2012 and Good Browser from Good Technology are now supported.
A major re-write has been done on the AJAX code to improve the performance on certain browser versions, please pay special attention to this area when testing.
We have created a beta community athttp://community.qlik.com/community/qlikview_beta_programs under “My Beta Programs” where you can download and test the beta, report bugs, start open discussions and ask questions.
The beta will run until April 30, 2013.
The Products Team
For QlikView 7 we developed a number of features that would enable developers to make even more advanced applications. One such feature was the Buffer prefix – a prefix that you could put in front of a Load or a SELECT that would store the data on the local machine and automatically use the local data when appropriate. With it, you could e.g. load data from a slow ODBC connection just once a day and for other script runs use the buffer.
The buffered data needed to be compact and something that QlikView could load fast. So, the QVD file was invented to solve this need. Today, hardly anyone uses the Buffer prefix, but QVD files created with the Store command are often used.
Another new feature was the Aggr() function. Already for QlikView 4 we had a solution for having an aggregation as dimension. Well, solution is perhaps not the right word… There was a kludgy, hidden feature with which you could use a count of a field as dimension. Internally it was called the Doctors’ Special. We solved a customer’s problem at the time, but we were not satisfied: we instead wanted a general, good solution for nested aggregations.
Six years later – after much thinking – Håkan (the Inventor) came up with the Aggr() function. It is a general function that can be used both as dimension and as measure. It can be nested and it can internally use any aggregation. In other words: it is a general function for nested aggregations. A by-product was the calculated dimension, which was necessary in order to use the Aggr() as dimension.
The Intel Itanium processor was first released in 2001, but its sales had still not picked up when QlikView 7 was released four years later in 2005. Instead, a new kid appeared on the block: The AMD X64 architecture. The X64 turned out to be both cheaper and faster than the Itanium, and as a consequence it sold better.
We already had an Itanium edition of QlikView and we realized that we also needed an X64 edition. Porting the code was straightforward and QlikView 7 was now shipped in three editions: X86, IA64 and X64.
QlikView 7 also brought the calendar object, the block chart, the box plot, the expression overview, the variable overview, the alerts and the reports.
As a curiosity, I can also mention that QlikView 7 was the first version with scroll bars for the sheet. None of the previous versions had had this. We had always had the opinion that scroll bars would steal screen space and not add any relevant functionality. Instead we had a zoom function so that you could fit the work area to the screen. But - it’s never too late to change one’s mind…
Further reading on the Qlik history:
Last month QlikTech released QlikView Expressor 3.9 which introduced some key features that not only strengthen data governance practices within a QlikView deployment, but also enable developers to extend QlikView Expressor functionality.
In this article I will briefly cover the QlikView Expressor Extension SDK and provide a supporting reference with examples that demonstrate how it can be used. (You can learn more about these features in this Technical Brief.)
Typically, software packages provide a method to extend their functionality using a development kit or API. This allows a developer to build in new capabilities that otherwise would not be available in the out-of-the-box software. The QlikView Expressor Extension SDK enables a set of toolkits and wizards that provide a framework with common functions for developing extensions for QlikView Expressor. With extensions, developers can provide clients with tools to integrate data from specialized sources and perform specialized transformations on data. An extension’s operators, connections and schema integrate into the QlikView Expressor Desktop interface and seamlessly work in conjunction with other standard, enterprise artifacts and operators.
The Extensions SDK provides a set of compilation, utility, and data type conversion functions using built-in Datascript Modules (DSM). DSMs are the standard QlikView Expressor scripting module for Datascript, based on the Lua open-source scripting language. Extensions built on these common functions add functionality to QlikView Expressor Desktop to support custom data sources and specialized transformations.
Figure 1 - The Extension Builder
A QlikView Expressor Extension is a plug-in (or add-on) that adds new Operators and Metadata artifacts to those already included in the core QlikView Expressor product. Extensions can provide read,write,transform and work-flow-like operations that are not available with the standard operators and artifact types. Once developed they can be easily packaged and distributed with the QlikView Expressor Extensions Manager.
Figure 2 - Custom Operators for reading files from a directory or FTP
Want to give it a try? Check out this tutorial and sample project to learn how extensions are built using QlikView Expressor.
NOTE: Please make sure you have QlikView Expressor 3.9.1 installed.
Samples available in the project include:
Senior Product Marketing Manager
QlikView and QlikView Expressor
When we start working on a new project, the customer requirements form the guiding rails for us to begin the process of designing. As we start brainstorming and throwing out ideas, we begin to fill the empty spaces with uncertain experiments. We then start making tiny decision which we stitch together part by part in trying to complete the big picture.
Initially to get started with drawing an outline of the project, we naturally tend to ask ourselves the basic questions of why, what, where, how. As the project progresses, we come across unforeseen hurdles, feedback, opinions and try to work our way through it to achieve the big goal. However, in the process of doing so, there are very strong chances of digressing from the main purpose of the project. In trying to put the small pieces together, and focusing on how to make it happen, we sometimes tend to lose the purpose of why we are doing what we are doing. This is when the question “Why” always comes handy to validate our work.
A design can never be a solution if it doesn’t fulfill the underlying purpose of its existence. Asking the question “Why” each time we complete our little milestones, that we set for ourselves, can do wonders to the final solution.
In the book called “The Shape of Design”, Frank Chimero points out - “Our mistake was the same as that of the creative person who places too much focus on How to create her work, while ignoring Why she is creating it. Questions about How to do things improves craft and elevates form, but asking Why unearths a purpose and develops a point of view. We need to do more than hit the right note. The creative process, in essence, is an individual in dialogue with themselves and the work. Why is usually neglected, because How is more easily framed.”
The process of design is most successful when it is an iterative process rather than a linear one. Asking the question “Why” at every stage to validate your work can not only help in creating a strong argument for your work but also help in delivering a legitimate story. So, a reality check by asking the question “why” at every stage of the process can help in creating the solution that one set out to provide in the first place.
Cultivating culture that emphasizes consistency and reusability is vital when introducing successful data governance practices. Common problems with many decision support systems are the amount of variation, redundancy and overlap that exists within the data models and business logic used across multiple analytical applications. These problems can delay critical decisions and disrupt IT operations while users struggle to verify the truth in data. Having data is one thing, having “good data” is another. With the volume of data increasing it is important to create a structured and consolidated data management layer that contains reusable and consistent definitions. This in turn gives developers and business users assurance that the data they are using, whether to develop applications or make decisions, is “good data”. It also expedites the process of creating new applications and eliminates much of the guesswork in maintaining applications as business requirements evolve over time.
Using QlikView Expressor (QVE) to manage and prepare data for QlikView is a great step towards adding data governance and data management to your QlikView deployment. Not only can you visualize where data originates and its final destination, but you can also create reusable parameterized business rules that can be shared across multiple applications.
By design QVE uses a Transform Operator to store Expression and Function rules to manipulate and add data. When transforming data - a simple QVE expression is used. The results yield transformed and/or new data columns to be used in the final output of the QlikView table model.
But what if you want to store and reuse an actual QlikView specific scripted expression and not just the resulting column output? This would be an ideal method to reference a single version of that expression in a unified manner. In turn it could reduce maintenance significantly if changes are made since there is only one place to make modifications, QlikView Expressor. This approach would also increase productivity and data confidence as it creates a single common expression stored in a centralized reusable repository.
Want to learn more and see it in action? Download the complete document and sample below.
If you are viewing this from http://community.qlik.com/blogs - you must click this link to get the sample:
The document is also available here: http://community.qlik.com/docs/DOC-4214
Michael Tarallo - Senior Product Marketing Manager
Bill Kehoe - Product Manager and founder Expressor
Knowing when to show more information and when to show less is not only good design it's good usability. The more information you present the greater the cognitive load a user has to juggle to accomplish a task. Sometimes you want to have lots of information visible to make the best choice but other times you don't. There is a point of diminishing returns where you have given your users too much information too soon. Sometimes people need to ease into an application, get acquainted with it, and then proceed to learn more.
Progressive disclosure is when information is sequenced out across several pages or screens to help a user process information and to avoid overwhelming them with too much information. Additional information, or more advanced or rarely used features, are hidden away until needed. This is a technique that was used by IBM in the 1980's when developing user interfaces. They realized that progressively disclosing additional tasks and information through a series of menus was better than having everything present up front. It managed complexity by clearing up clutter. It helped new users get familiar with the UI and as they became more savvy users they used the menu systems to find more advanced functionality.
The attached Technical Paper discusses a bit more how progressive disclosure is useful in BI. Progressive disclosure helps the DAR methodology to give users the general summary on the Dashboard, more advanced functionality on the following pages, and then the real deep dive information for Reporting. Progressive disclosure helps you design for other people at a variety of skill levels to get the most out of your applications.
May 6th, 2011 at 3 AM: I was watching our real-time web analytics report as the web address for QlikCommunity was redirected to a new server. It was reporting “0 Visitors" for a few minutes…then, I started seeing visitors from Germany, the Netherlands, Finland, Sweden and all across Europe and Asia…the new QlikCommunity was alive!
We are really proud to bring you the new QlikCommunity, powered by the Jive Software SBS Platform. This new site is a product of months of research, user testing and programming work, and I am extremely happy with the way it turned out. I’ll be doing some more posts in the near future about all of the cool features of our new QlikCommunity, but I’d like to highlight a couple of my favorites so you can check them out now:
We are still working on some of the new features, and we thank those of you who have sent in questions or issues, as that has helped us with the transition. We are continuing to work on making all of the changes, and we will have them completed soon.
As a final note, I would like to send a special thank you to our User Acceptance Testing group (UAT), who helped us test and debug the site before we went live. We invited around 60 of our top community members to help, and received great feedback about the content, interface and design of the site. We at QlikTech appreciate the time and assistance you put in to the process, and the entire community appreciates your input in helping us make the new QlikCommunity as helpful and easy to use as possible!
Thanks again to all of our 55,000+ QlikCommunity members for making this such a great site, and here's to more great days ahead!
We are currently in the process of testing version 11.2 with Windows 8, 2012 Server and also Internet Explorer 10 with a view to introducing support (which may be limited) for the above in a future 11.2 Service Release. Retrospective support in version 10 and already released v11 Service Releases will not be added.
We would advise users of Windows 7 not to upgrade their Internet Explorer browser to IE10 at this time. Be aware that Windows Update may automatically install IE10. Some known issues with IE10 include (use as a guide only, not an exhaustive list):
The Products and Support Team
We are excited to announce the availability of QlikView Expressor 3.9 and the QlikView Governance Dashboard 1.0. Please access the links below for more detailed information.
The Global Products Team
There have been significant and beneficial updates to the QlikView Governance Dashboard since its Beta 2 release in December 2012. These updates include new KPIs, support for multi-node QlikView clusters, alert indicators, improved data lineage as well as navigation and usability improvements.
Review the Governance Dashboard 1.0 technical brief for more detail.
QlikView 11.20 SR1 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). In addition to addressing over 100 bugs in the 11.20 code, this release also incorporates the bug fixes addressed in the 11.0 service releases, bringing into full alignment the 11.0 and 11.20 releases. Going forward, all new Service Releases for QlikView 11.x will be in the 11.20 code stream only.
The initial 11.20 SR1 build , 11.20.11716 has been replaced by a new build, 11.20.11718. There are two reasons for this new build
If you have used 11.20.11716 without any evidence of memory increase during reloads then it is not necessary to install the new build. We apologize for any inconvenience
Please report any issues to the QlikTech Support group through the normal channels
The Products Team