Is this the right place for this data?
It can be tempting to try to build everything into one document to save on QlikView licenses. Here, we will explain why this is not a good strategy.
Background
There are often good reasons to want to cram as many features or disassociated data as possible into a single QlikView document, but this is rarely the best strategy and can ultimately lead to difficult and expensive rewrites. Keep logically different applications in separate documents and take the hit on QlikView license costs because, ultimately, this will be cheaper and save you lots of time.
How to do it
We can't always anticipate how a QlikView document will evolve, and even the best-designed application could eventually become unwieldy and inefficient over time. Often, this is caused by adding in data and features that would be better in a separate document. It's common to see QlikView documents that should logically be two or more documents, with unrelated data models or simply...
