I have a qlikview document that's doubling my claculations on certaint items. When I do an item count it shows the number of items doubling. This only happen on some items which is hard for me to comprehend. Example of problem item is PTR-400TCBL or WPL-22PB. Working items is wpl-1000a or wpl-1000
Somewhere along the line an inner join has the secondary table generating 2 rows for 1 row in the primary.
Do you really need to do all those inner joins to create one table? Why not keep the tables seperate and let Qlikview manage the relationships on the key fields?
But I dont see any calculations anyway? The 'preceding load' runs after the SQL Select so removing the inner joins (which are using the resident table on which you could perform calculations) would just create seperate tables.
You may be able to just look at the log file to see when the duplicate rows appear. You can also try commenting out parts of the script to see which load is causing the problem. There's nothing wrong with joining a bunch of tables together, but if you have two rows for a single ID in one of the tables, it will duplicate all of the other data from all the other tables as well. If that's not what you want, you'll need to either not join that table, or perhaps do a group by, or a distinct, or some other way of getting only the one row you want.
