Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Want to see what's currently in public preview? We've pulled it all together in one place. Check it out here
cancel
Showing results for 
Search instead for 
Did you mean: 
orlando162
Contributor II
Contributor II

Aggregate Outer Join data into 1 row only

Dear all,

I'm going crazy with joins:

Schermata 2022-06-24 alle 12.01.45.png

I would like to aggregate joined dimensions into a single row.

I used [ID_Invoice] as common dimension to create outer join. It should be so easy for you, sorry I'm pretty nearbie about these things.

Labels (1)
3 Replies
marcus_sommer
MVP
MVP

There is a missing/wrong association in regard to the field/dimension "Project" and/or a data-quality issue.

You might just remove this field from your table to get a single row. Otherwise if this information is important for this view you will need to look on your data and/or adjusting the data-model.

- Marcus

orlando162
Contributor II
Contributor II
Author

The association is made with the field [ID_Invoice]:

 

[Sirio]:

LOAD
[Mandante] as [Company],
[Data] as [Data_Registrazione],
[Data] as Master_Data,
[Importo (CHF)] as [Importo_CHF],
[Importo (Valuta)]&'_'&[Numero documento] as [ID_Invoice]

 

OUTER JOIN ([Sirio]) LOAD
[Project],
[# Invoice],
[Amount],
[Amount]&'_'&[# Invoice] as [ID_Invoice]

marcus_sommer
MVP
MVP

The effect which you see may not only be caused from this join else also from other script-parts and/or of the fields which are used within this table.

Further it looked as if you are combining a measure-field and an ID-field to a key-field. If so it's quite unusual and I suggest to check if this approach is really expedient.

Beside this I suggest to add definite unique id's within the loads, for example with recno() and rowno() and then using a table-box with all relevant fields to see which associations are really there and how the data-quality looked like.

- Marcus