topic Re: Enhanced Pivot Table in QlikView

Enhanced Pivot Table

lucasdavis500 — Thu, 16 Mar 2017 18:45:48 GMT

Hi, is it possible to create a table like this in Qlikview? I can't seem to get the mechanics down, it seems that if I resolve one solution I run into another problem, and surely I am not the only user who would like to see data in this manner:

# CREATED BY TYPE	2/5-2/11	2/12-2/18	2/19-2/26	2/27-3/4		TOTALS	% to Total
Type 1	1	2	3			6	2.0%
Type 2
SubType1	4	5	6			15	5.0%
SubType2	7	8	9			24	8.0%
SubType3	10	11	12			33	11.0%
SubType4	13	14	15			42	14.0%
SubType5	16	17	18			51	17.0%
SubType6	19	20	21			60	20.0%
SubType7	22	23	24			69	23.0%
TOTALS	92	100	108	0	0	300	100.0%

mainly I would like to have a Totals Column, and then a % of total column. The Date and Type are dimensions in this chart, with expression being where the #'s come from. Does qlikview allow you to see % as well as TOTAL # at the same time?

Re: Enhanced Pivot Table

Anonymous — Thu, 16 Mar 2017 19:10:52 GMT

Re: Enhanced Pivot Table

lucasdavis500 — Fri, 17 Mar 2017 13:30:48 GMT

Well played, any way to do this without a calculated dimension?

Re: Enhanced Pivot Table

sunny_talwar — Fri, 17 Mar 2017 13:54:54 GMT

Another similar approach (still uses calculated dimension, but you may or may not find it easier)

Used Robin's sample (thanks Robin)

Re: Enhanced Pivot Table

lucasdavis500 — Fri, 17 Mar 2017 14:24:25 GMT

These both seem like acceptable answers. Sunny, I found yours to be easier to use, I couldn't manage to get Robin's to work. I don't understand why Qlik's tabular formatting can be such a pain... I think many end users would like to have a TOTAL column and a TOTAL % column for a reference, without having to switch all of their values in fields to %....

Re: Enhanced Pivot Table

Anonymous — Fri, 17 Mar 2017 16:06:53 GMT

there's a "dirty" solution possible without calculated dimension:

You could do a join on the dummy table for building a cartesian product and then you divide every value by the number of fields in the dummy table (in this example 3)... but this will sooner or later lead to mistakes...