![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi: Per mirosoft documentation, incrementally processing a dimension should not offline a cube, however, when I inrementally process a dimension and I have Cube open in Microsoft Pivot Table. As soon as analysis server is done processing a dimension, numbers on the pivot table change to "Invalid Values". After I use refresh on Pivot Table, numbers come back. This will not work because if user has a cube open and we incrementally process a dimesion. All of a sudden user will see Invalid data on the pivot table. Per microsoft documentaion, this should not happen. Has anyone come across this? How can fix it? Any help is greatly appreciated. Thanks |
#3
| |||
| |||
|
|
It doesn't take the cube offline when a dimension is incrementally updated; it expires the data you currently have open (invalid values). The values are invalid since the dimension has been updated. All you need to do is run the query again. We experience the same thing here and I've never heard any complaints about it. I actually prefer having to run the query again since the data may have become invalid since the last reprocess. "Sal" <Sal (AT) discussions (DOT) microsoft.com> wrote in message news:5B16EB87-E268-4B36-B18D-5D23BCE3DFF0 (AT) microsoft (DOT) com... Hi: Per mirosoft documentation, incrementally processing a dimension should not offline a cube, however, when I inrementally process a dimension and I have Cube open in Microsoft Pivot Table. As soon as analysis server is done processing a dimension, numbers on the pivot table change to "Invalid Values". After I use refresh on Pivot Table, numbers come back. This will not work because if user has a cube open and we incrementally process a dimesion. All of a sudden user will see Invalid data on the pivot table. Per microsoft documentaion, this should not happen. Has anyone come across this? How can fix it? Any help is greatly appreciated. Thanks |
![]() |
| Thread Tools | |
| Display Modes | |
| |