Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I have two files Project and Sale.
Project has many rows for the same ProjectID. Atleast 8 to 9 rows for each ProjectID as it has fields such as Areacode etc that changes for each row. Therefore there are 8 to 9 rows.
Now I have another file called sale that has ProjectID and saleID in it and it may have more than one row for each project as there are multiple saleID.
Q) My question is based on the above scenario explained on the data present in two files, if the join is made on the ProjectID . saleID will be commented to avoid synthetic key, is this correct?
2) If I pull all fields into a table box both Sale and Project fields - all in a table box, there will be many rows for each project because of existing 8 to 9 rows on area and now more rows because of the saleID . So totally if there are 16 rows and the rows from saleID table have distribute d themselves for each row in the project file with Areacode table, is this correct data as that is what qlikview would do. Please let me know if this is correct and there will not be any data issues.
Urgebtly required. Please answer bv below each point.
In point1 in Q) above saleID from second file Sale will be commented and SaleID in project file will remain as it is - is this correct way of doing this.
In point2, we are getting multiple rows of project because of existing 8 to 9 rows due to different area code and now because of different saleID the no. Of project rows has doubled . All this is beiNg default done by qlikview. Is this correct data - No need to bother about this join am I correct - do let me know as I am new to this and understanding data.
Please answer both questions under each point. Thank you. Urgently required
Please avoid posting your request multiple times - and then with different amount of information given.
It's hard to follow a discussion and a waste of ressources.
Instead, focus on one thread per question and give as much information as possible.
Sample records and your requested result are valueable information and could help to speed up getting an answer.