the reason being because your index calculation is getting computed as Table down try to change the compute using customer for index Filter hope that should solve the issue
Hi Naveen, unfortunately this didn't work.
Hi John thank you for your reply. You are definitely correct. Does this mean that there is no way to accomplish what I am trying to do?
when you drag the region field to the viz you created another partition -you need to account for that in your calcualtion
I tried to do that but something is going on with the workbook - It won't let me write any LOD formulas - is there something in the book blocking lod"S
Hi Jim, thank you for your reply. Is Level of Detail a new feature? I am using Tableau 10 but the example I shared was from Tableau 7 I believe.
1 of 1 people found this helpful
There is an issue I LOD's have been around since 9 - so there is an issue - will recreate it and send something over
Nick see the attached - it is in 10.2
the problem here is a little more complex than it looks and thanks to Jonathan Drummey's "painting with numbers'
The addition of region combines with the sparse data (i.e. not all combinations have a data value) throws the index count off
the way to address the problem is create a calculated field using Index() (don't just put index() in the viz)
the set up the calculation as shown below
then open the Advanced on the drop down (it is on the bottom)
next move in customer and region
click ok on on the from screen the "At The Level " (the level where the indexing is to take place)
and None for restart
on the filter
Ok now the viz will look like this
and it will produce this
and this for 2/3
If this posts assists in resolving the question, please mark it helpful or as the 'correct answer' if it resolves the question. This will help other users find the same answer/resolution. Thank you.
index issue.twbx 2.4 MB
Jim, This is great! I learned 2 things out of this:
1) Although I always knew you could change the default table calc by clicking the blue link, it never occurred to me that it uses the traditional table calc dialog box! (what I call the rubiks' cube) For some reason I still like this dialog box better then the newer one.
2) Creating a separate calc field Index() to be used inside another calc field makes a difference! I did learn long ago when nesting table calcs it makes a difference to create separate calcs for them but is this a nested table calc? It is the same table calc used twice by condition. Can you explain in layman terms why setting the original one shown below does not produce the same result?
Thanks a million Jim, your explanation was great and despite not being able to open your worksheet, your solution has fixed the problems in my workbook. Your help is greatly appreciated!
I always like your posts - well thought out -
but the real star here is Jonathan
Don't know what version of Tableau you are on now but I would highly recommend moving to at least 10.3 -
LOD's and Mapping are some of the functions that are greatly improved