If you are reading this chapter voluntarily, you must be a technical person who enjoys the process of getting your hands dirty and writing code. And if you aren’t that sort of person, don’t worry! QlikView is not as technical as you may think. In fact, it’s non-technical, for the most part.
In this chapter, you look under the hood to see how the magic happens. You’ll get to prepare that magical associative data model that allows your users to navigate data with ease. You will build the foundation that allows them to paint the world in green, white, and gray.
At this point, you know the business requirements from Chapter 3. You even know what kind of visualizations you are going to develop, from Chapter 4 (which is, by the way, a luxury that you don’t usually have in real life). Now, buckle up and let’s load some data!
As you know by now, QlikView needs to load data into its associative data model, which in turn will be loaded into memory for visual analysis. The process of loading the data is specified in the QlikView load script, which is managed in the Script Editor.
Chapter 5 mentioned the term ETL (extraction, transformation, and load). The QlikView script language covers all three parts of ETL. In a mature QlikView environment, you may choose to separate the three processes into distinct layers (there are merits to doing so, and we will cover those best practices in Chapter 10), or ...