Qlik Community

Ask a Question

QlikView App Dev

Discussion Board for collaboration related to QlikView App Development.

Support Cases coming to Qlik Community Oct. 4! Start chats, open cases, explore resources: READ DETAILS
Showing results for 
Search instead for 
Did you mean: 
Creator II
Creator II

Need Clarification

Hi All,

Actually i am working on Existing Application. I have so many issues on that.

My datamodel very clumsy, almost 70+ tables.

Again we are doing scratch from data, i have many tables.

I am thinking about create one Table.

everytime is it possible to create one table using ETL process???

Please give me suggestion's..

2 Replies


You can LOAD tables and use JOIN or Residents to create one unique table.


Creator III
Creator III

In that case joins and resident loads will be a great help for you. It's had to determine how complex this operation would be - 70 tables into 1?

Try to keep things as simple as they possible can be - dropping every field that was only a temp field or you don't use it at all - I would start from checking the QV Document Analyzer created by Rob Wunderlich

Search Recipes | Qlikview Cookbook

This will definitely help to determine what fields aren't used in your app and what objects are resource heavy in your front end.

My last advice - try to replace some of the joins with ApplyMap() function. If you only need to bring across a small number of columns from one table to the other - do it with ApplyMap() and drop the original tables.

Start from joining/ApplyMap() on the dimension tables and just see if that's matching your expectations. You might also notice that at the end of your work you will decide to stick with a star schema data model rather than one table - if you will search trough Qlik Community you will definitely find some articles about all pros and cons for each solution. Good luck!