I've recently moved jobs and with that, primary development platforms to Qlik Sense. I used QlikView a bit early in my career, but for the last five years it's been all Power BI.
Qlik Sense is mostly great, but I am struggling with the mentality shift - having been embedded in DAX I automatically come at every problem thinking about tables and filter contexts, rather than set analysis. A lot of the time it doesn't matter too much (in simple contexts, defining a set is not that different to filtering a table) but with complex problems (e.g. a measure that requires iterating over subsets within a set) it has repeatedly caused me to get myself into a real twist.
Has anyone made a similar transition, and if so can you recommend any tips or tricks to get me thinking in a more 'Qlikish' manner?
Apologies if this is in the wrong place - I know this probably belongs in a Qlik sub, but they all look a bit dead.
Solving complex challenges within the report-layer regardless if it's DAX or set analysis is IMO too late because all essential logic belonged into the generator + data-model layer and within the UI remain mainly simple expressions like sum(Field) maybe with simple additional filter to ignore/overwrite certain selections or dimension-layer.
Beside this you may on top of a set analysis also need various aggr() constructs to define sub-sets of the data. A good starting point to this topic would be the various blog-postings from HIC:
