Recent Blog Posts

• 

  Design

  Maps and Mazes: A Tale of Two Extensions

  The highly respected (fictional) scientist, Ian Malcolm, once chastised a group of scientists for being “so preoccupied with whether or not they could that they didn't stop to think if they should.”  Ignoring the fact that this statement was made in regard to ferocious dinosaurs that would soon terrorize mankind, there is truth held within for how we approach technology.In this business we’ve all been guilty at one time or another of using the “m... Show More

  The highly respected (fictional) scientist, Ian Malcolm, once chastised a group of scientists for being “so preoccupied with whether or not they could that they didn't stop to think if they should.”  Ignoring the fact that this statement was made in regard to ferocious dinosaurs that would soon terrorize mankind, there is truth held within for how we approach technology.

  In this business we’ve all been guilty at one time or another of using the “more is more” approach in data visualization.  All too often we marvel at something that dazzles without stepping back for a minute to consider the story that’s actually being told by the data.  This is especially true with QlikView extensions.

  There are a plethora of JavaScript libraries that display data in exciting and dynamic ways.  It flies here and there, spins, zooms, explodes, and distracts attention for a bit before the viewer attempts to decipher the information loosely assembled in the chaos.  With extensions we sometimes jump at the opportunity to cram a hot, buzzy technology into QlikView simply for the bragging rights. Sometimes what is needed is something much simpler.

  When I began working on an extension to visualize medal counts for the Olympic Games this past summer, it was assumed that I would use a slick mapping UI similar to Google Maps or OpenLayers.  These powerful mapping tools allow developers to perform a wide variety of complex geospatial tasks, taking into account curvature of the earth, map projections, tessellation, and a variety of other things that will induce sleep in the average human being.

  In order to achieve the effect of highlighting and coloring the different countries for this extension, it is not as simple as telling the Google Maps API to select country X and highlight it with color Y.  These mapping tools do not have country or region boundaries prepackaged.  Due to this fact, the actual longitude and latitude points for the boundaries of each and every country would need to be found and plotted as shapes on the map.  Not only is this a LOT of data for JavaScript to handle, geographical data is not easy to come by.

  So, let’s take a step back. The question that needs to be asked is how much additional detail will users need?  The data we’re looking to visualize is not geographic in a technical sense.  We only need to display the countries of the world as concepts and entities, not as precise geographic objects.  In this case, the precision offered by the mapping tool is completely irrelevant, as is the map itself beneath the plotted shapes.  Why repurpose a complex and powerful mapping tool to draw a picture? Instead, why don’t we just, you know, DRAW A PICTURE?

  Fine, but how do we do that? Enter SVG.  SVG (or Scalable Vector Graphics) is a form of vector imagery in XML format which draws shapes and lines as a series of paths.  While this format is not supported by all browsers (ahem…Internet Explorer), fortunately there is a JavaScript library called Raphaël that will draw SVG paths in old and new browsers.  Finding an SVG of the countries of the world was relatively easy, and from that point, I leveraged Raphaël in drawing the image.

  Rather than explain further in great detail how I coded and created this extension, what’s more important is to emphasize the need to consider the goals of our data visualizations.  Just because we’re showing a map, must we use a mapping tool?  Clearly not, and by drawing the world map as SVG, we used the appropriate tool.  Our visualizations should yield to the data.  If the data is trying to tell a story, we should get out of the way and let it tell its tale.

  For a more in depth and technical overview of the extension, please click here for a zip file containing the extension and a technical brief.

  Show Less

  By Brian_Munz 2012-09-20 / 11:25 AM

  4 4908
• 

  Design

  Actionable Metadata – with QlikView Expressor

  Actionable DataIt should come as no surprise that in order for raw data to break free from its deluge and become truly actionable - it must go through a number of steps before it is finally ready for decision makers. Steps can include various methods that access, combine and transform the data to make it meaningful for Business Discovery. Traditionally, methods that make data actionable can include a combination of data integration applications (... Show More

  Actionable Data

  It should come as no surprise that in order for raw data to break free from its deluge and become truly actionable - it must go through a number of steps before it is finally ready for decision makers. Steps can include various methods that access, combine and transform the data to make it meaningful for Business Discovery. Traditionally, methods that make data actionable can include a combination of data integration applications (ETL) and/or QlikView data-readiness procedures (QlikView Script). These methods in turn prime QlikView’s powerful associative in memory data layer used by all QlikView deployments. QlikView and knowledge workers are then responsible to turn that actionable data into useful information to help drive decisions.
  

  Metadata in Action

  With the introduction of QlikView Expressor, data provisioning for QlikView deployments has been redefined. Whether you are simply accessing data from a warehouse or combining data from disparate sources, QlikView Expressor will provide both actionable data along with actionable metadata as you develop. This makes managing data for QlikView more efficient, less prescriptive and will ensure a higher degree of data confidence and reuse across all QlikView applications.

  Metadata is typically defined as data about data. Active metadata on the other hand, can be defined as "metadata in action". Traditional Business Intelligence metadata is mostly static and limited to only describing a few properties about the data it references - such as sources, data types, column names, length and format. QlikView Expressor metadata is not static, it’s active.  It describes common properties about the data while also actively respecting  rules that have been defined on its attributes.

  Let’s take a simple example using a string column named ZIP used to store a 5 digit +4 zip code.  Not only can the metadata describe the attribute using a common business term such as PostalCode, but it can also specify a minimum and maximum string length constraint to ensure the data length only falls within the specified range. Furthermore, it can provide a pattern match rule using a regular expression such as ^\d{5}-\d{4}$. This will ensure that the data flowing to QlikView will absolutely match the XXXXX-XXXX pattern. -  What if the data fails the rules? A choice to set a corrective action to use a default value or even redirect the record to be captured is available, allowing more control on where and how the data is processed. Other examples can include using an allowable list of values, setting rounding / min / max / precision / scale / constraints on numeric values, date range validation, date formatting and string padding / truncation. 

  Using active metadata with QlikView Expressor is just one part of the overall QlikView Expressor solution. Combined with other key capabilities, you will discover how QlikView Expressor can help simplify your QlikView application development and create a reusable environment that reduces development time and speeds up your deployment efforts. Come back to this blog often as I will be covering these capabilities and much more in future articles.

  

  Figure 1:  Managing Active Metadata with QlikView Expressor

  
  

  Mike Tarallo
  Senior Product Marketing Manager
  QlikView Expressor

  Show Less

  By Michael_Tarallo 2012-09-14 / 04:00 AM

  1 3123
• 

  Support Updates

  Version 11 Service Release 2 Beta is now closed.

  Hello QlikView users!A big thank you to all those customers and partners who downloaded the version 11 SR2 Beta.The Beta is now closed and we look forward to shipping Service Release 2 soon.Thank you for your help!Global Support Team

  By Greg_Hood 2012-09-06 / 05:37 AM

  5 3103
• 

  Design

  A Historical Odyssey: QlikView 3

    Oh, glorious were the days! Businesswise we were perhaps not yet so successful, but product maturity made giant leaps forward. QlikView 3 was a very good product packed with new features that made life easier. Both developers and users loved it. It was easier for prospects to evaluate it and it was easier for us to sell than previous versions. QlikView 3 was released in the spring of 1997, in time for the yearly IT exhibition CeBIT in Hannover.... Show More

   

  Oh, glorious were the days! Businesswise we were perhaps not yet so successful, but product maturity made giant leaps forward. QlikView 3 was a very good product packed with new features that made life easier. Both developers and users loved it. It was easier for prospects to evaluate it and it was easier for us to sell than previous versions.

  QlikView 3 was released in the spring of 1997, in time for the yearly IT exhibition CeBIT in Hannover. In version 1 and 2 we had focused on the UI (user interface) – on presenting data in such a way that a user could explore it and learn from it. For QlikView 3, we had changed focus slightly. We now worked more on simplifying the data loading process and the development of the document. We also made it easier for people to try out the product by introducing a 15-day evaluation license. As a result, more and more people started developing applications with QlikView. And it became much easier to convince prospects and partners to join us on our journey.

  

   

  One major change in QlikView 3 was the Automatic Outer Join. Already in QlikView 1 and 2, you could have a data model with several tables. But the associations between the tables were like inner joins and no analysis was possible for values that lacked corresponding records in a neighboring table. For instance, customers that had no orders in the Orders table were always grayed out. But with QlikView 3 it became possible to select such customers. This is a feature that we today take for granted, but it was not there in the beginning.

  Another change in QlikView 3 was that the scripting language developed immensely. We introduced a number of new script constructs. Join, Concatenate, Crosstable, Intervalmatch, resident load, preceding load, Group by, Peek, Previous, and Variables the way we know them today, all arrived in QlikView 3 – as did the text file wizard and the possibility to load files over the internet. You could now make fairly complex data transformations right in the QlikView script.

  We also introduced several new sheet objects in QlikView 3 (line chart, scatter chart, multi box, straight table and table box) as well as new property dialogs – one for user preferences, one for the sheet, and one for the document itself. And you could right-click on the sheet and get a float menu. It became a whole lot easier to navigate around all the product settings.

  

   

  On top of all this, we released French and German language versions of QlikView, as well as a Macintosh edition. Yes, we had a Mac version of QlikView! However, we didn’t sell much of it and since it meant a lot of extra work for R&D, both in terms of development and test, we discontinued it one release later.

  And – most importantly of all – QlikView 3 was extremely stable.

  As a curiosity, QlikView 3 also had one of the best error messages ever: “Time Travel is not allowed!” Anyone can figure out when this was used?

  

   

  HIC

   

  Further reading on the Qlik history:

  A Historical Odyssey: QlikView 2

  A Historical Odyssey: QlikView 4 and the first Server

  Show Less

  By hic 2012-09-04 / 12:08 PM

  7 5220
• 

  Design

  Why it is ok to scroll

  A popular topic in interactive design is that of scrolling. When is it ok to scroll? Is it ok to scroll? Will people know they can scroll? What information should be above the fold?Above the foldWhen web design began the designers were mostly trained print designers since interactive design was a new field and "web" designers didn't exist. The concept of "the fold" is one that print designers imported from newspaper design. The goal of designing ... Show More

  A popular topic in interactive design is that of scrolling. When is it ok to scroll? Is it ok to scroll? Will people know they can scroll? What information should be above the fold?

  Above the fold

  When web design began the designers were mostly trained print designers since interactive design was a new field and "web" designers didn't exist. The concept of "the fold" is one that print designers imported from newspaper design. The goal of designing "above the fold" was to keep the most important headlines and images in the top half of the newspaper so when it was folded in half at the newsstand the most enticing information would be visible and passers-by would stop and buy the paper.

  With the internet the concept of designing web pages with the important information above the fold, keeping key information viewable without scrolling vertically, was met with a new challenge: monitor variety. When a publisher produces a newspaper every customer gets the same sized paper. The content that is above the fold for one reader is the same for every reader. With web design the variety of monitors, browser chromes, and resolutions is so diverse that there is no standard height for where the fold begins. The fold on my phone is alot different than the fold on my 27inch desktop monitor. The ipad has not one but two folds: one in portrait orientation but a shorter fold in landscape orientation.

  Ignore the fold

  People's fear is that important information will never be found if it is below the fold. That somehow people (not themselves of course) don't know how or when to scroll to find additional information so the solution must be to cram as much content at the top of a page as possible. This is ridiculous. Usability tests continue to prove that not only do users scroll but scrolling can actually improve the user experience. If people feel they are on the right track they will continue to scroll for content.

  Advice:

  • Design pages that are legible and attractive. If your application is well designed it encourages people to explore the document and they will scroll on their own.
  • Vertical scrolling only. While users can scroll vertically as well as horizontally, generally speaking a page should do one or the other and people prefer vertical scrolling. Vertical scrolling is a more standard method of navigating content as well as the simple fact that most scroll wheels move vertically and not horizontally. Vertical scrolling is just easier.
  • Monitor Resolution. To avoid horizontal scrolling you should know your intended audience. I use analytical data to find the largest number of users with the lowest common resolution and design for that. 1024x768 is still a decent standard size as well as being the resolution of the ipad in landscape orientation.

  Show Less

  By N/A 2012-08-14 / 06:45 AM

  0 5792
• 

  Design

  Ready, Set, Go with QlikView SAP Netweaver® Connector

  Since we introduced the first version of the QlikView SAP connector 6 years ago, many of the QlikView customers leveraged the power of QlikView with the SAP data. Through QlikView’s unique, in-memory associative technology, they are able to make SAP based business decisions with the speed of the business.The key enabler of the solution is the certified QlikView SAP Netweaver® Connector, which can extract data from SAP® R/3®, mySAP™, SAP BW, and B... Show More

  Since we introduced the first version of the QlikView SAP connector 6 years ago, many of the QlikView customers leveraged the power of QlikView with the SAP data. Through QlikView’s unique, in-memory associative technology, they are able to make SAP based business decisions with the speed of the business.

  

  The key enabler of the solution is the certified QlikView SAP Netweaver® Connector, which can extract data from SAP® R/3®, mySAP™, SAP BW, and BEX queries into QlikView. The extracted data  can  be combined with non-SAP data in one QlikView application providing a 360 degree view of the business.

  Let’s take a look at a business case and understand how the QlikView SAP Netweaver® Connector would help. Assume a company has various SAP Netweaver data stores and its users would like to do sales analysis across their business.  With SAP Netweaver® Connector they can connect and extract data from;

  • SAP BW/BI Business Explorer Query for sales information
  • SAP Data Store Object (DSO) for additional order values and shipping weights
  • An SAP Query to gain insight into sales organization detail metrics
  • An SAP R/3 Table so they can integrate the company details into Google maps
  • An SAP Extractor for customer items
  • An SAP BAPI for business area lookups
  • An SAP Report for customer payments

  They can then create visual and flexible analysis with this data in one single QlikView application which  can also integrate data from external non-SAP data sources.

  QlikView provides pre-packaged QlikStart templates for SAP R/3 as well as QlikView SAP data dictionary and QlikView script builder applications. These apps would give a good head start for IT by delivering the background database information of how tables within SAP interact. It would also enable the business users to quickly realize their own data in ways they may not have envisioned before.

  

  Last month we introduced a new version of the QlikView SAP Netweaver® Connector (SAP Netweaver version 5.7) with even more capabilities. If you would like to have a jump start to do Business Discovery with your SAP data, you can download the QlikStart templates from QlikCommunity.

  Show Less

  By elif-tutuk 2012-07-16 / 05:08 AM

  3 3943
• 

  Design

  Colour

  Are you colourblind? Do you actually know if you’re colourblind?  On the 3 occasions I have presented on this topic I have had a two male attendees admit to not knowing….. (until now...) that they were colourblind to some degree.It is estimated that approximately 8% of men and 0.5% of women are colourblind. This large difference in probability is due to the fact that the genes that produce photopigments are carried on the X chromosome; if some of... Show More

  Are you colourblind? Do you actually know if you’re colourblind?  On the 3 occasions I have presented on this topic I have had a two male attendees admit to not knowing….. (until now...) that they were colourblind to some degree.

  It is estimated that approximately 8% of men and 0.5% of women are colourblind. This large difference in probability is due to the fact that the genes that produce photopigments are carried on the X chromosome; if some of these genes are missing or damaged, color blindness will be expressed in males with a higher probability than in females because males only have one X chromosome, whereas women have two!
  (http://en.wikipedia.org/wiki/Color_blindness)

  The most common way to determine level of colourblindness is to take an Ishihara test. The test consists of a number of plates that contain patterns of different coloured/shaded dots. These dots form to show numbers and shapes that you can…. or in the case of colour blind people…. can’t see.

  Can you see a number in this plate…… I can’t…. I am actually colourblind, which is quite ironic considering I work with QlikView visualisations every day. A person with “normal” vision should see the number 6, colourblind people will see nothing.

  

  You can take the tests online on a number of websites :

  http://www.tedmontgomery.com/the_eye/colortst/colortst.html

  http://colorvisiontesting.com/ishihara.htm

  http://www.colour-blindness.com/colour-blindness-tests/ishihara-colour-test-plates/

  One great example I found is the image below. I cannot see any difference between the two images due to me being Red-Green colourblind. People in the office who have perfect vision could see a massive difference in the colours.…

  

  (Source: http://facweb.cs.depaul.edu/sgrais/colorvisiondefi.htm)

  I often find that colour and the use of colour is something that is decided upon without much thought, hence me writing this. We have to be very careful when we decide on the colours we use in our charts and dashboards. In your QlikView objects, really think carefully about colours and the impact your choices will have on your users.  Ensure you use colour blind friendly palettes, and avoid using colours that are “close” together in tone, next to each other in charts such as scatter and bar charts.

  There are a number of resources on the web to help you choose friendly colour palettes..

  http://jiminy.medialab.sciences-po.fr/tools/palettes/

  http://colorbrewer2.org/

  So, choose your colours wisely, try not to use colours that are “close” together. Utilise the web resources to help determine your palette. If, like me, you are colour blind then these resources are a massive help!

  Remember the number…. 8% of males are colourblind…this is a big number. This 8% could be the key decision makes or indeed the developers.

  Wherever possible, colour should purvey meaning, not just used because it looks nice!

  See more about this topic in this techincal brief Colour
  

  ABY

  Show Less

  By N/A 2012-07-12 / 03:36 PM

  1 7298
• 

  Support Updates

  Version 10 Service Release 5 is now available

  Hello QlikView users,We are pleased to confirm that Version 10 Service Release 5 is now available on our download site http://eu.demo.qlik.com/download/.We encourage Version 10 users to move to Service Release 5, build 10.00.9516,  which has undergone the longest testing and beta program of any Service Release.  Release notes for Service Release 5 are attached.    Always follow industry best practices when upgrading your software.If you are using... Show More

  Hello QlikView users,

  We are pleased to confirm that Version 10 Service Release 5 is now available on our download site http://eu.demo.qlik.com/download/.

  We encourage Version 10 users to move to Service Release 5, build 10.00.9516,  which has undergone the longest testing and beta program of any Service Release.  Release notes for Service Release 5 are attached.    Always follow industry best practices when upgrading your software.

  If you are using Version 9, remember support ends 31 October 2012.

  Thank you for choosing QlikView!

  Global Support Team

  Show Less

  By Greg_Hood 2012-07-04 / 01:32 AM

  0 3017
• 

  Design

  An Inside Look at Building QlikView Extensions

  Have you ever wondered what it takes to create QlikView extensions? Here’s someone who knows: Brian Munz, QlikView extensions “imagineer,” as I think of him. His official title is web technology lead on the demo and best practices team. Brian was the lead developer for the current version of demo.qlik.com and the version of AccessPoint that ships with QlikView Server in QlikView 11.Since QlikView 10 (released October, 2010) QlikView has enabled c... Show More

  Have you ever wondered what it takes to create QlikView extensions? Here’s someone who knows: Brian Munz, QlikView extensions “imagineer,” as I think of him. His official title is web technology lead on the demo and best practices team. Brian was the lead developer for the current version of demo.qlik.com and the version of AccessPoint that ships with QlikView Server in QlikView 11.

  

  Since QlikView 10 (released October, 2010) QlikView has enabled customers and partners to create extensions; web developers can bring custom and third-party data functionality or visualizations into QlikView, where they become fully interactive just like native capabilities. “Some of the cooler extensions I’ve seen,” said Brian, “are very powerful in terms of utility. It’s not solely about custom visualizations. You can use extensions to connect on the back end to other products (like Google Analytics) or add a Twitter feed or button, or detect browsers and devices . . . those kinds of things.” Brian has built mapping extensions, which plot regions on map (colors and shades them) based on data points, using Google Maps and open source mapping tools. He also created a geolocation extension, which enables the app to find the user’s current location (check it out here).

  I asked Brian what it takes to build QlikView extensions and here’s the way he put it: “A lot of work is around answering the question, ‘What am I trying to show?’ Once you figure that out, it’s about connecting to the data. Web developers often deal with SQL and MySQL — with databases with rows and columns. With a QlikView extension, the data comes into the extension the same way. Once you get the syntax right for pulling the data out of the source system, you say, ‘Oh, I know how to do this. I've done it a million times before.’ You then have to decide how the extension should communicate back to QlikView. A web developer who has worked with Ajax or JavaScript APIs can learn to do this without too much headache.”

  To create extensions, you need some level of JavaScript coding proficiency. To create a fairly simple extension, you could search for code snippets and paste them together. If you want to do something more complicated, you need heavy-duty JavaScript coding skills. It also helps to have a general level of comfort with other Web technologies like CSS and HTML.

  How long it takes to build a typical extension object? “There really isn't ‘typical,’” Brian said. “It depends what the extension object is. If it's enormously complicated it could take months. If it’s simple, like a marquee that scrolls across the top of the screen, showing KPIs, that could be done in an hour. Creating an extension that’s a map that has different regions of the country showing up in different colors takes longer, compared to just integrating with an existing JavaScript library.” Building QlikView extensions can take as little or long as any web project.

  “The beauty of it,” Brian said, “is in the combination. Web technology is extremely powerful, and so is QlikView. Having them work together seamlessly increases the total full power of QlikView.”

  Show Less

  By N/A 2012-05-21 / 04:01 AM

  4 7762
• 

  Design

  Let the User Select

  QlikView is about empowering the user. Allowing a user to freely choose what to look at and how to look at it is one of the cornerstones of Business Discovery. Another is about simplicity – which often translates into removing unnecessary technical obstacles so that the user can focus on the data and the information that lies hidden in it. This often leads to a situation where you have two different user roles: an application developer and a busi... Show More

  QlikView is about empowering the user. Allowing a user to freely choose what to look at and how to look at it is one of the cornerstones of Business Discovery. Another is about simplicity – which often translates into removing unnecessary technical obstacles so that the user can focus on the data and the information that lies hidden in it. This often leads to a situation where you have two different user roles: an application developer and a business user, where the application developer takes care of the data modeling aspects of the analysis and the user interacts with the data, asks questions and finds new areas of exploration.

   

  In such a situation it is important that the developer treads carefully – he or she must remove technical obstacles without limiting the user. However, in an effort to simplify, application developers sometimes complicate things without realizing it. Let me give you a couple of examples.

   

  

   

  Macros and Actions are features that unfortunately sometimes are used to “help” the user make the right selection. I have often seen developers create buttons that make selections and activate other sheets, or triggers that clear selections and make new selections when you leave a sheet. Such constructs are confusing for the user, who doesn’t understand why these new selections happen. Macros and Actions often obscure the QlikView logic and prevent the user from learning how to interact with data on their own.

   

  Another area where the power to select can be taken away from the user is when Set Analysis is used. In set analysis, the developer can define a formula with an arbitrary selection that overrides the one made by the user. Often the new selection is based on the user selection. Set analysis is necessary for calculations that extend outside the user-made selection, e.g., if the user wants to make a year-to-date calculation for the time up to the selected month. Properly used, it is an extremely powerful tool that enhances the user's ability to find information in data. But I have seen cases where set analysis instead replaced the user's selection and limited the his ability to interact with data. To hard code the selection inside a formula is in some cases disrespecting the user’s intelligence!

   

  My view is that navigation – choosing a sheet, activating sheet objects, expanding branches in pivot tables, and, most importantly, making selections – should be left to the user. Constructions that “help” the user in this area usually have the opposite effect. Instead of helping the user, they often complicate the interaction with data and confuse the user.

   

  I am convinced that macros, actions and set analysis sometimes must be used, but these features should be used with caution. They should never be used for things that the user can do better. We live in an age of empowerment, and users want to be free to explore data in their own way and on their own.

   

  QlikView should allow them to do just that.

   

  HIC

  Show Less

  By hic 2012-06-26 / 04:00 AM

  7 4943
• 

  Support Updates

  End of Support for Version 9 is rapidly approaching * REMINDER * 31 October 201...

  Support for Version 9 ends on 31 October 2012.    If you are running Version 9, please make sure you upgrade to Version 10 or version 11 in good time.Thank you for choosing QlikView!Global Support

  By Greg_Hood 2012-06-05 / 05:14 AM

  1 2305
• 

  Support Updates

  Version 11 Service Release 1 Update 1 now available

  Hi everyone,Version 11 Service Release 1 Update 1 has been made available for download on our download site.   We apologize for the delay in releasing SR1 - details on the bugs fixed in this Update are included in the release notes.Release notes can be downloaded from here http://d1cf4w4kkla6tb.cloudfront.net/qlikview/11.00/11282/QlikView%2011%20build%2011282%20SR1%20Update%20Release%20Notes.pdf.Thank you for using QlikView.Global Support Show More

  Hi everyone,

  Version 11 Service Release 1 Update 1 has been made available for download on our download site.   We apologize for the delay in releasing SR1 - details on the bugs fixed in this Update are included in the release notes.

  Release notes can be downloaded from here http://d1cf4w4kkla6tb.cloudfront.net/qlikview/11.00/11282/QlikView%2011%20build%2011282%20SR1%20Update%20Release%20Notes.pdf.

  Thank you for using QlikView.

  Global Support

  Show Less

  By Greg_Hood 2012-04-13 / 01:34 AM

  0 3616
• 

  Support Updates

  Version 11 Service Release 1 now available

  Dear QlikView users,We are pleased to announce that version 11 Service Release 1 is now available for download http://global.qlik.com/download/.Service Release 1 [SR1] contains approximately 160 customer reported bug fixes plus fixes for additional internally detected bugs.   SR1 full build number is 11.00.11271 and release notes are attached.   Before upgrading or installing version 11 please make sure you read the release notes and follow indus... Show More

  Dear QlikView users,

  We are pleased to announce that version 11 Service Release 1 is now available for download http://global.qlik.com/download/.

  Service Release 1 [SR1] contains approximately 160 customer reported bug fixes plus fixes for additional internally detected bugs.   SR1 full build number is 11.00.11271 and release notes are attached.   Before upgrading or installing version 11 please make sure you read the release notes and follow industry best practices regarding installing and upgrading software.

  Thank you for choosing QlikView!

  QlikView Global Support

  Show Less

  By Greg_Hood 2012-03-20 / 05:59 AM

  2 3871
• 

  Support Updates

  QlikView Update Alert

  We recommend that all users implement this update without delayWhat: A full list of fixes and changes, including description of a security fix is included in the release notesWho: All QlikView 11 and QlikView 10 SR3 and SR4 usersWhere: http://global.qlik.com/download/How:  Follow the "Upgrading QlikView Server" instructions in the QlikView Server Manual and QlikView ManualOnce both Developer and QlikView Server are upgraded, recreate QVDs [by run... Show More

  We recommend that all users implement this update without delay

  • What: A full list of fixes and changes, including description of a security fix is included in the release notes
  • Who: All QlikView 11 and QlikView 10 SR3 and SR4 users
  • Where: http://global.qlik.com/download/
  • How:  Follow the "Upgrading QlikView Server" instructions in the QlikView Server Manual and QlikView Manual
    • Once both Developer and QlikView Server are upgraded, recreate QVDs [by running the load script to store the QVD files again] and open and  save QVW files in Developer or reload them with Publisher/Server as soon as practical.
    • Customers running V10 SR3 who are not planning to upgrade to V10 SR4 should contact QlikView Support to obtain a patch regarding the security fix.
    • If you have any problems upgrading your QlikView installation and have a valid maintenance contract, please contact QlikView Support.

  QlikView Support Services

  Show Less

  By Greg_Hood 2012-01-05 / 11:55 AM

  0 3306
• 

  Support Updates

  QlikView Version 10 Service Release 4 now available

  Hi everyone,We are very pleased to confirm that version 10 Service Release 4 (SR4) has been released by R&D - 10.00.9274.   SR4 is an extensive release with possibly the longest list of fixes of any service release to date.   See the release notes attached for details of fixes.   We strongly encourage you to upgrade to this service release.   If you do, make sure that you follow industry best practices applicable to upgrading any production envir... Show More

  Hi everyone,

  We are very pleased to confirm that version 10 Service Release 4 (SR4) has been released by R&D - 10.00.9274.   SR4 is an extensive release with possibly the longest list of fixes of any service release to date.   See the release notes attached for details of fixes.   We strongly encourage you to upgrade to this service release.   If you do, make sure that you follow industry best practices applicable to upgrading any production environment!

  You can download your QlikView software here: http://global.qlik.com/download/.

  Thank you for choosing QlikView!

  Global Support Team

  Show Less

  By Greg_Hood 2011-12-02 / 02:32 AM

  2 8477
• 

  Support Updates

  SAP Connector 5.6 now available

  We are pleased to announce the release of our latest SAP Connector, version 5.6.    Please visit our download site for the installation fileshttp://global.qlik.com/download/Enhancements to the SAP Connector include:An additional Connector for SAP ExtractorsSUBSELECT on Cluster Tables now possibleLookup function for variables in BeX queriesKind regardsGlobal Support Support

  By Greg_Hood 2011-10-06 / 06:23 AM

  3 2881
• 

  Support Updates

  Version 9 SR7 Update now available - build 9.0.7808

  We are pleased to confirm that the latest Update build for version 9 SR7 is now available on our download site http://global.qlik.com/download/.An Update is a build which rolls together several bug fixes (or patch builds) in to an official release which replaces the previous Update for version 9, build 9.0.7778.   An Update is subject to basic regression testing on the code changes implemented.The release notes attached detail the fixes implement... Show More

  We are pleased to confirm that the latest Update build for version 9 SR7 is now available on our download site http://global.qlik.com/download/.

  An Update is a build which rolls together several bug fixes (or patch builds) in to an official release which replaces the previous Update for version 9, build 9.0.7778.   An Update is subject to basic regression testing on the code changes implemented.

  The release notes attached detail the fixes implemented in this release.   Thank you for choosing QlikView!

  regards

  Global Support Team

  Show Less

  By Greg_Hood 2011-09-07 / 11:55 PM

  0 2826
• 

  Support Updates

  Version 10 SR3 updated - build 10.0.9061 available

  Hello everyone,Unfortunately some defects were detected in version 10 SR3 build 10.0.9055 so we have released an Update which corrects them.   Build 10.0.9061 can be downloaded from http://global.qlik.com/download/.The Update corrects the following:QEMC - "Index was out of range" message boxSome Publisher tasks were reset by the upgrade to new scheduled date 2012-01-01In some circumstances, QV Developer would hang when changing items in the User ... Show More

  Hello everyone,

  Unfortunately some defects were detected in version 10 SR3 build 10.0.9055 so we have released an Update which corrects them.   Build 10.0.9061 can be downloaded from http://global.qlik.com/download/.

  The Update corrects the following:

  • QEMC - "Index was out of range" message box
  • Some Publisher tasks were reset by the upgrade to new scheduled date 2012-01-01
  • In some circumstances, QV Developer would hang when changing items in the User Preferences, Object tab

  We sincerely regret any inconvenience caused and assure you that we are working hard at preventing these defects slipping through.

  Thank you for using QlikView.

  Global Support Team

  Show Less

  By Greg_Hood 2011-07-12 / 11:36 PM

  0 7154
• 

  Support Updates

  QlikView Version 10 Service Release 3 is now available

  We are pleased to announce that SR3 is now available for version 10.See http://community.qlik.com/blogs/technicalbulletin/2011/06/30/qlikview-10-service-release-3-available-build-9055You can download the installation files and release notes from http://global.qlik.com/download/.Always read the release notes and installation instructions before making any changes to your system!

  By Greg_Hood 2011-07-01 / 04:55 AM

  0 3167
• 

  Support Updates

  Important information about End Of Support

  Hello and welcome to the QlikView Support Updates blog.   This entry provides important information about End of Support for QlikView Software versions.Currently Supported Versions of QlikViewVersion 11QlikView Version 10 support ends November 2013QlikView Version 9 support ends October 2012Major Version Support PolicyQlikView provides support for a major version of the software for a minimum of 2 years from the date that major version is replace... Show More

  Hello and welcome to the QlikView Support Updates blog.   This entry provides important information about End of Support for QlikView Software versions.

  Currently Supported Versions of QlikView

  • Version 11
  • QlikView Version 10 support ends November 2013
  • QlikView Version 9 support ends October 2012

  
  Major Version Support Policy

  QlikView provides support for a major version of the software for a minimum of 2 years from the date that major version is replaced by the next major version.   For example, version 9 was replaced by version 10 in October 2010.   Version 9 support therefore expires 2 years after that, in October 2012.

  Thank you for choosing QlikView!   If you would like to raise a support case, please log in to the customer or partner portal.

  Direct Customers - http://www.qlik.com/us/services/support/customer-portal

  Partners - http://partners.qlik.com/

  Show Less

  By Greg_Hood 2011-06-10 / 01:20 AM

  0 5422