The simplest solution is to not join the tables and just let Qlik associate them through the common field name. Assuming sales is in Table A it will sum correctly. A simple UI table with Sum(Sales) and Field B as the dimension will show the Sum(Sales) amount correctly per row but potentially misleading to users as the sum of the rows may not equal the overall total. This is because a given sales amount may be associated with more than one row.
The best solution really depends on the nature of the data and the underlying business logic that is appropriate.
Hi Rehan, When you have one to many relation then join is behaving exactly as it supposed to do. so In qlik there are two option to cater this issue. 1. Instead of using join just associate both table on key fields
2. Use Mapping load and ApplyMap() instead of using join it will get the first value of B field against A field available in the table.