Skip to main content
Woohoo! Qlik Community has won “Best in Class Community” in the 2024 Khoros Kudos awards!
Announcements
Nov. 20th, Qlik Insider - Lakehouses: Driving the Future of Data & AI - PICK A SESSION
cancel
Showing results for 
Search instead for 
Did you mean: 
suvechha_b
Creator III
Creator III

How to exclude "division_key" from expression

Hi,

How can I exclude the "division_key" from the inbound expression:

"sum({<[division_key]=>}ordered_quantity)"

But we can see from the below screenshot that in the "inbounds" , "blockedstock" are not linked with "division_key","SEP".

Capture.PNG

How to solve this problem.

Sample attached.

7 Replies
sunny_talwar

Not sure I understand your concern, would you be able to elaborate and point in your document what is the concern?

suvechha_b
Creator III
Creator III
Author

Capture1.PNG

The report is having "Division".

But my Inbound Orders is not linked with "Division" thus it is showing null. How can I write the expression so that the

expression of "Inbound" doesn't depend on "Division".

ThornOfCrowns
Specialist II
Specialist II

I would first suggest you have a look at the data to try to eliminate the multiple synthetic keys you have in that schema.

sunny_talwar

So you are trying to get rid of 9143 number? May be use 'Suppress When Value is Null' for the Division dimension?

Capture.PNG

suvechha_b
Creator III
Creator III
Author

But I need the Model depends on [Trans Date]

means every day records to be stored.

suvechha_b
Creator III
Creator III
Author

Sorry, you didnt understand me. I doesn't want to get rid for the value "9143".

My datawarehouse is having the following data :


Capture3.PNG



You can see that my datawahouse is not having division. But I need the "Division" in my report.


and I need the data as,

everyday,


[Trans Date] [Value]

20160401    100

20160402     200


...


20160525  500.



ThornOfCrowns
Specialist II
Specialist II

I'm not saying drop the data, I'm saying you should look at why you've so many synthetic keys in your schema.