Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Sorry for the wall of text. I am new to QLIK and mainly have SQL background. I was told QLIK is based to some degree on SQL. But there are few things it does that I need clarification on. Unfortunately, I don't have access to their QLIK dashboard yet have a limited data to work with. Below are the filter issues they are running into. Note that they are using this same load for about 12 different bar charts and donuts on one dashboard
Filter behaviors and current issues:
- filter on gains, then losses => Gains filter removed [should remain]
- filter on losses, then Top schools => Losses filter removed [should remain]
- filter on Top Schools, then (common) STRL => filters work together
- filter on Top Schools, then STRL, then GSE => filters work together
- filter on TS, then STRL, then GSE, then Gains.Hiring Authority => all filters (but gains) removed [should remain]
- filter on gains, then STRL => filters work together
- filter on STRL, then losses, then another dimension of losses => filters work together
^ seems common filters work with any 1 set, but any dataset-specific filter does not work with any filter from other datasets
I suggested they only load in one table each instead of loading two copy's each of the the Onboard, Gain, and Loss and then use a JOIN. But they told me that QLIK( see their comment under previously) already does the JOINS for you. Currently it looks like they are concatenating everything so I'm not sure if this overrides the JOIN? Below is the load they are currently trying to do and I'm wondering if they are going about this correctly? I see QLIK has something called set analysis where you can script the filter behaviors. Not sure if this would be a good option here?
// effecting 2 separate counts (cols) for each dataset.
as per above script loading data from different source files based on some conditions and concatenating all into single table then In front end created charts based on the requirement
the issues you mentioned are related to the Datamodel and not the script
if possible share some sample app and also a brief of how each dataset is associated with each other
understanding the data ,its relations and the use cases that it needs to support are critical when building the Datamodel