Use of dimensions in Straight table

[bhaskarsharma03]

Hi,

I have seen people using dimensions in Expression (in Straight Table). Is there any advantage in doing so?

eg: keeping Region, Department, Country etc directly in expression along with measures like Sum(Sales), Sum(Budget)...

What I have been doing is keeping only the measures (where aggregation is required) in the Expression, and keeping all the other fields as Dimensions.

Could anyone throw some light on what advantage/disadvantage of either of the method over the other?

Regards,

Bhaskar

[hic]

The dimensional values define how many records the straight table is going to get. If you want one record (or more) per value of a field - if you want the field to span the cube - then you need to use the field as dimension. See more on http://community.qlik.com/blogs/qlikviewdesignblog/2013/03/25/dimensions-and-measures

If you have a field as expression, it implies Only(field). See more on

http://community.qlik.com/blogs/qlikviewdesignblog/2013/08/06/it-s-all-aggregations

http://community.qlik.com/blogs/qlikviewdesignblog/2012/08/03/the-only-function

HIC

[Clever_Anjos]

As Henric Cronström says, if you NEED that your dimension 'spans the cube', you must use as dimension.

If that field is unique to each combination, you can use it both as dimension or only() expression.

Sometimes, I face performance differences, so I usually try both and check which one performs better