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

Announcements
Join us in Toronto Sept 9th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
ivonna01
Contributor
Contributor

Cross Table: 2 Rows and 2+ columns

I looked at similar posts and I tried to apply provided solutions but it didn't work. 

I need to do cross table that contains 2 header rows, and the data contains multiple columns.
See attached. 

To the kind person that can help me - can you please post the solution as text in the body of this topic (I'm never able to open Qlik files provided in this forum)

Thank you

 

Labels (1)
3 Replies
lorenzoconforti
Specialist II
Specialist II

if a solution were possible in your case, it would be complex and delicate (i.e. it might stop working if you were to add/remove columns)

the best advice I can give is to work at the source, either requesting data formatted properly or formatting it yourself before loading into Qlik Sense

ivonna01
Contributor
Contributor
Author

I think below thread showcases that the solution is possible.

https://community.qlik.com/t5/New-to-Qlik-Sense/Crosstable-with-two-columns-and-two-rows/m-p/1305267

However, in post#1305267 the columns are additionally split (into year and something, and year and something else) - I don't need that kind of split.
And since DATE in my case is not part of the cross table, I don't need to worry about it becoming a "string/text" 

My understanding is that I need first to combine two header rows, second pass load it as "cross table" and third pass, separate data into 3 "columns"

I'm still trying to figure out how to re-purpose this solution to fit my file. 

 

lorenzoconforti
Specialist II
Specialist II

That solution relies on columns not changing/being added. As soon as you add an extra month or remove something,it will stop working. As I said, a solution to loading your file might be found but the fundamental problem is with how the data has been structured in the excel file. Rather than trying to fix in Qlik what is not fit for purpose, I'd rather fix it in excel.