Qlik Sense table: Sorting on date-time field makes randomly data disappear and /or the total to change value
Article Number: 000085288 | Last Modified: 2019/10/21
Sometimes sorting a straight table's column that contains a dimension such as a date, the user could experience the loss of some rows or the total to change value.
Since there is NO set analysis or an expression that could explain such a behavior, what could explain this? In order to troubleshoot something like that we need to check, if there are any limitations set on the column which limits the rows. Limitations that could have been set on the column in combination with sort order could exclude rows and eventually change the total amount. As you may know the limit is determining if a row should be grouped under "other" or not.
For example if the limit is 10 and if our date dimension is below that the row might or might not count as an Others... depending on the sort order. This could be also troubleshooted with Sum and Auto in totals and explains why we could experience different results between Sum and Auto for the total function. Sum is a sum of the rows you see giving possibly a reduced total, and Auto since will include the others (that are hidden) could give a different value.
Qlik Sense Enterprise