I have a detail table as well as a summary table(s) I want to load into Qlikview. The issue I am having is the summary table will like to multiple fields within the detail table causing a synthetic key. How can I avoid this situation. I want to be able to bring in the summary data, so I can have better performance.
guytanguay wrote:I have a detail table as well as a summary table(s) I want to load into Qlikview. The issue I am having is the summary table will like to multiple fields within the detail table causing a synthetic key. How can I avoid this situation. I want to be able to bring in the summary data, so I can have better performance.
I'd only load summary data as a last resort. I'd try just about anything else first to improve performance. That said, I also don't see anything specifically wrong with your summary table or synthetic key. It seems like a natural consequence of having both summary and detail data, and I wouldn't expect it to cause problems. Are you seeing problems?
This has helped me with the summary table however it has caused another problem with loosely coupled keys. I need my summary table to work off my master calendar as well as my project data. However, when I name my summary date field the same as my master calendar table I get loosely coupled key, and no data shows for my summary in my graph.
You are creating a loop in the data model that you need to eliminate.
First, let me say that I agree with John that the ideal solution would be just to use the detailed information and dynamically sum information in the reports.
Your problems could be fixed if you concatenate the Summary Table with the Detail Table where the corresponding columns between the 2 tables have the same name (Remove the composite key). You might also need to add an additional column that acts as a flag that tells you if the row is summary or detail (eg. 0 = summary and 1 = detail)
However, this solution may greatly increase the size of the file in RAM because alot of columns are going to be filled with null values and null values appear to take up some space.
If the data volume is high then you might think about creating 2 QV applications: 1 for summary data and the other of detail data. You can link the 2 applications with a button/action that will transfer the current selection when the user navigates to the other application making it feel like the same application.
Putting the summary data in the detail table with concatinate does not fix my problem because of the date field. This is where I am getting tripped up and that is the cause of my looping of the data model.
Can you give me an example of this being done? I like the idea. I am having a very difficult time implementing the aggregation of data within an expression.
