Keep in mind that Qlik will match every row from the LEFT table with every row from the RIGHT table, if they have the same values of the Key fields - hence the duplication. With that in mind, you should analyze your data and decide carefully, what tables should be joined and what tables should be left separate.
For example: You may have Order Lines (many lines for each Order) and Order Shipments (many lines for each Order). If you can't match these two tables 1:1 by Order Line Number, you will be joining many lines to many shipments. So, if you have 10 lines and 8 shipments for the same order, a Join will produce 80 rows.
So, pick and choose what tables should be joined, and what tables shouldn't.
Another possible issue to investigate is the meaning of the ID field. Some databases use the same field names in different tables, and they mean different things. The field ID in the Suppliers' table means Supplier ID, while the field ID in the Orders Table means Order ID. If this is the case, then you need to rename some of these different fields accordingly.
In data modeling, you always have options. You just need to know the implications of different options.
As to further help, it's hard for me to do without diving deep into your data and understanding the different data entities and how they relate to each other. You need to get some basic understanding of Qlik data modeling, and then this task will get easier for you.
Look for a Qlik data modeling class, or for a good book. My book "QlikView Your Business" is one of them - it teaches all important Qlik development techniques, including data modeling - from the basics to the very advanced level.
Hi Thanks for the suggestion, this is not simple join between the tables...i am using MondoDB collection which is creating arrays collection, each array qlik has segregated separately finally based on the common key those arrays collection need combined into one transaction table and almost 30 arrays collection show's 30 tables.
Anyway I find the solution, thanks for the reply and suggestions
Your explanation sounds like these arrays load parts of the same transaction table into individual tables. If this is the case - each table represents a part of the same transactional table, then the solution is to CONCATENATE them, rather than JOIN them. In that case, they will all get appended into the same table, without any attempt to match the keys.
