A paradox development is that we often spend more time troubleshooting QlikView applications than we do developing them. Such is the case that if nobody complains about an incorrect calculation or missing data, then they probably aren't using what we've created. When we become aware of a potential problem, we also tend to invest more time understanding and searching for the anomaly than we do fixing it. Even though this is time well spent when we encounter an issue for the first time, we should avoid repeating the same investigation every time the same issue reoccurs.
In this chapter, we are going to review several common anomalies that occur when we perform data analysis and visualization in QlikView. We document their possible causes and solutions as we would in a knowledge base that we create to help save time when we come across the same issues in the future. Let's cover the following topics to improve our QlikView troubleshooting skills:
Troubleshooting...