Skip to main content

QlikView App Dev

Discussion Board for collaboration related to QlikView App Development.

Announcements
CUSTOMERS ONLY: Now accepting customer applications for the 2023 Luminary Program: SUBMIT NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Forced *inclusion* instead of exclusion?

I have an expression for which I can use forced exclusion to ignore/remove certain dimensions. For example:

SUM({$<Product=,Type=>} CallCount)


In that case we can get the CallCount without taking any Product or Type selections into consideration.

However, it is possible that this list of exclusion fields will have additions/deletions/changes in future builds as client data changes. So rather than causing a maintenance headache in which expressions would need to be updated from month-to-month, is there a way instead to create an expression that simply specifies which dimensions to pay attention to, rather than which to ignore?

For example, if I only want my CallCount sum to include considerations from the dimensions "DetailType" and "MonthID", and ignore all others that may be in the table (Product, Type, etc) - is there a way to do this?

Thanks!

1 Solution

Accepted Solutions
simenkg
Specialist
Specialist

Yes.

SUM({1<Product=$::Product,Type=$::Type>} CallCount)

This expression will ignore ALL selections except Product and Type.

View solution in original post

1 Reply
simenkg
Specialist
Specialist

Yes.

SUM({1<Product=$::Product,Type=$::Type>} CallCount)

This expression will ignore ALL selections except Product and Type.