Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I've run into an issue with a pivot table that I am at an absolute loss for. I have created a pivot table with 150 dimensions, and 10 expressions. Each dimension and expression is conditionally displayed, which allows the user to create a custom view into the data. The issue has come in when I add the 128th dimension. When I add this dimension, the expressions move from being columns to being rows. I've tested different dimensions to see if it was something about the field, but no matter what fields I use, the addition of the 128th dimension causes the pivot to move the position of the expressions. After the expression move to rows, there is no way for me to select those fields and try to move them back to the column position. I've looked through all of the documents settings and I can't see anything that would set the pivot table to work for only 127 dimensions. Is there a limit on the number of dimensions that will successfully display in a pivot? Has anyone run across this or have any idea what can be done to fix this? Any help would be fantastic. Thank you.
Is it really necessary to allow so many dimensions at once? I recommend to use a restriction (probably by a macro), not allowing to select >127 dimensions. Or even better, no more than 20...
Hi Travis - did you ever find a solution to this? I'm running into the same issue with a pivot and a large number of conditionally enabled dimensions/expressions. I've found that you can get the expressions to snap back in place but there is no rhyme or reason - you kind of just have to randomly drag and drop until it works. And of course this only temporarily fixes it as I've noticed they'll get thrown back out of place on Access Point.
Hi Mark,
what version you are using ?
Roland
11.2 SR5
Hi
I have the same problem and use the 11:20 SR7, you've got feedback about the solution?
Tks
Hi
today I got confirmation that the problem with the pivot table is a bug and has been surveyed with the ID 66058. I don't know when it will be fixed but I hope for the next SR.
Hi Marco - we were essentially told that the R&D team will look at it but no ETA on a resolution.