I am partial to this of course, but since I have worked with other legacy BI tools I have something to compare it to, I would not want it any other way.
Check these resources out and let me know if we are getting closer to satisfying her concerns, I think our new visual data prep in 3.0 including the ability to define your own relationship or override the recommended associations will help answer some of them.
- Qlik Sense in 60 - Visual Data Preparation - YouTube
- Qlik Sense 3.0 - Creating a Custom, Composite, Compound Key - YouTube
- The Associative Experience - Revisited
- Qlik Sense - Selections that make "Sense"
- Seeing Shades of Gray Just Got Easier | Qlik
Please mark the appropriate replies as CORRECT / HELPFUL so our team and other members know that your question(s) has been answered to your satisfaction.
Thanks for the prompt reply. Appreciate the resources you've gathered for me.
So, If I were to explain to my co-worker without confusing her much, could I be wrong in suggesting that the way QlikView associates the data is tantamount to "performing a full outer join"?. Where every entry is preserved. (Or, is this an oversimplification of the actual idea behind Qlik's AD?)
I personally never had to get into these microscopic questions, because Qlik's handling of data was so versatile and intuitive.
But your suggestion helps.
YES, that is a great way to explain it, especially for those who may be used to SQL based tools and data modeling. We tend to not use that term often when describing the modeling experience, because we like to differentiate ourselves from the legacy BI tools and sql-based query tools.
Glad I could help.
Stay well my friend.