Skip to main content
Announcements
Global Transformation Awards! Applications are now open. Submit Entry
cancel
Showing results for 
Search instead for 
Did you mean: 
Sera
Contributor III
Contributor III

Total Value changes with displayed dimensions

Hallo everyone, 

the total amount in my (straight) table is changing, when i'm adding/removing a specific dimension (see the screenshots below/attached, where i have used the "Show column if"-function to simulate the same thing):

There's no need for actively selected filters. The Formula for Measure "Lagerbestand (01)" is:
= sum({<Firma = {'01'}, LBVKL_test = {'J'}, [VMI Kunde] = {'J'}>}[Menge Bestand])

Further information: 
- all (relevant internal) tables are connected with each other in the data model (and i checked it like 100 times 🤐 )
- Totals function for the measure is set as "Sum" (not auto)
- QlikSense Server Version: 13.21.9   (April 2019 patch 2)
- The correct value should be around 417.000 (so the greater value)
- Converting the straight table to pivot-table, always show the smaller (most likely wrong) of the 2 values... 

Does anyone have an explanation for this strange behaviour and an idea how to fix it? I need it as straight table.

without the columnwithout the columnwith the columnwith the column

As pivot (with and without the column)As pivot (with and without the column)

Labels (1)
6 Replies
jerifortune
Creator III
Creator III

Have you checked your data model? It would be nice if the sample qvf file is shared here.

StarinieriG
Partner - Specialist
Partner - Specialist

Hi,

maybe is it unable "include null value" for the other dimensions?

Sera
Contributor III
Contributor III
Author

I already checked the data-model countless times and hours already... 

 

can't provide a QVF with data (since there is customer data in) and i don't know how much it help without, but here's a sample QVF without the data (and reduced to the 2 straight tables + 2 test-wise pivot-tables)

Sera
Contributor III
Contributor III
Author

i checked every measure, every field, every table, just everything like 5 times to be extra sure about including/excluding null-values (in sight of: the tick-symbol is set in all settings)

Sera
Contributor III
Contributor III
Author

++ UPDATE ++

We have tested pretty much EVERYTHING now. In hope that someone can solve the problem, i wanna share our observations: 

  • We have made 4 tables: 2 Pivot, 2 Straight.
  • All contain the same dimensions and the same (single) measure
  • In datamodel, everything is connected with each other (no data islands)
  • In 1 Pivot & 1 Straight table, i don't show the field/dimension "Kundengruppe" anymore (set "show column if" to 0)
  • Totals function of the measure is set to "Sum"

The one full-info straight table (with showing "Kundengruppe") shows a bigger number. 
The remaining 3 (straight table & the 2 pivot) tables show a smaller number. 

  • including/excluding of null values and/or zero values didn't change the total number at all
  • changing the Totals function of the bigger-number straight table  to "Auto" changes the number to the smaller amount (the same, like in the other 3 tables)
  • changing the Totals function in any other table doesn't do anything

 

Currently, we think the bigger number is the correct one, but i need the same total value to be shown for ALL levels of detail. Different people need different views, but these total numbers shouldn't depend on the amount of displayed dimensions...

kdmarkee221
Contributor III
Contributor III

I'm running into something similar, except for me I am running an IF statement inside of an expression that has set analysis and seeing the same behavior where the column total keeps changing depending upon my selected dimension fields.  I found this post (https://community.qlik.com/t5/QlikView-App-Dev/Using-if-condition-in-an-expression/td-p/637253) and tried a few things from it but I haven't found the solution yet, and maybe there isn't one in my case because it could be that my data model is too complex to pull this off.  Not to state the obvious but conditional statements are the common theme here, but how Qlik handles it (or if it can) in certain cases seems tricky.