Introduction

Data modeling in QlikView is usually quite straightforward. Often we will need to rename some fields to prevent associations that shouldn't be there, or rename a field to make an association.

Sometimes we are faced with a situation where things are not quite easy. There may be multiple fact tables with multiple associations to other tables that cause the "dreaded" synthetic key or, worse, a data loop.

A good data model in QlikView is often very different from one that might be built for an operational database. Often the best design approach is quite akin to dimensional modeling. Depending on the complexity of the data, a hybrid of approaches is necessary and QlikView is flexible enough to support this.

In this chapter, we will examine strategies to deal with these more complex associations.