Since Qlik Sense is completely indexed - both text and numeric - all fields no matter what - the necessity for cubes are not there actually. Cubes are a way of explaining and creating a limited number of indexes for OLAP systems that orginally worked towards disk.
Due to the in-memory fully index nature of the Qlik Associative Model you can make any combination of fields into. So you think of it as a dynamic cube creation without any limits.
Slicing and dicing in Qlik are achieved directly with the built-in visual objects as (almost?) any selection will do a slice/dice and recalculate on the fly.
Thank you for the response.
There are many dimensional levels created in the cube each having different levels. As the cube pre-calculates each measure at all levels and store that aggregated information in memory for quick results(eliminating calculations during the run time). As the qlik do aggregations during the runtime, will it not cause any performance degradation ?
Is there any way to auto calculate at each level and store in a memory for Quick insights ? do we have any option to schedule and refresh data in regular intervals in such way for all dimensions and measures are calculated?