Pivot Table.

[#1]

Hi i am new to Qlikview.

I am trying to create a Pivot Table.

My Table has 4 fields. Country , Person_name , Attribute , Value.

I want to generate a pivot table for all the person whose Height is 6 feet for Country Argentina.

I know i can do it throgh Macros. But want to avoid Macros. As it is not good for Very large data.

Uploading my QlikView for ur better understanding. Looking for a Response.

Regards

Raj

[disqr_rm]

See enclosed. Would this be fine?

[#3]

Hi Rakesh , Thanks for ur Quick Response , But i do not want any hard coding like Value=6 in the Expression.

I wanted to select any number of multiple Conditions like

No_of_friend > 12 for a diffrent Country , may be UK .

And it should be a pivot Table with columns as the Attributes.

The table that u have made do not have other attributes of those persons with Height=6.

[#4]

Hi Rajesh , There is also another Solution to it

by Concatenating Attribute & value with Person_name , to get the desired result.

Where a person select " Height 6 " from temp_column field and can generate the pivot table.

But in this way we will not be able to further select , like Height 6 "and" No-of_friends > 12.

So i want to avoid Both , Macro and the above solution.

[#5]

Please find my QVW file to

[Anonymous]

Raj,
The problem is in your data structure. What you need is instead one field Attributes to create separate fields Age, Hight, etc., and the values in these fields will replace your Value field.
See attached

[#7]

Hi Michael ,

You Soluion is very user friendly and has given me new dimension of creating Datastructure design .

But the Problem is if we have a lot of Attributes like say 662 , and all lies in 1 table(with Rows say 1 Billion) , then is very difficult as the second pass load on the Resident Table (Actual_Table). will be a time consuming operation.

Regards

Raj.

[#8]

It will put a lot of Load on the server as well.

[Anonymous]

Raj,
See another version. Here the number of attributes can be any, it's not hardcoded but is read in a loop.
As for the server load, it 's usualy a good idea to move the hevay work on the reload process rather on the fornt end calculations.

[Oleg_Troyansky]

Raj,

since you are new to QlikView, it's important to learn the "QlikView way" from the very beginning and not make costly mistakes...

You see, QlikVIew is an on-line analytic tool - not a Data Warehouse, not a Report Writer, but rather an anlytic tool that allows visualizing trends and helping users analyze their business.

662 attributes across 1 Billion records - doesn't sound like QlikView kind of solution... I bet you cannot produce any meaningful analytic solutions over 662 attributes. Usually this is happening when you don't get enough direction from your Users (or Clients), so you are loading all available data, just in case.

Somewhere along the line, though, someone has to sift through 662 attributes and determine the dozen or so of important ones and leave the rest aside.

just an observation...

Oleg