Users are experiencing issues where they slice data to Excel 2003 and the data sliced out does not match what is in the cube. Same users also experience problems where numbers in their reports are incorrect, but cube numbers appear fine. This error occurs across multiple cubes and users and impossible to replicate.
We have tried re-installing TM1, Excel and re-imaging hard-drive to no success.
Has anyone else come across this issue? Or have a solution?
TM1 Slice data does not match cube data
- jim wood
- Site Admin
- Posts: 3951
- Joined: Wed May 14, 2008 1:51 pm
- OLAP Product: TM1
- Version: PA 2.0.7
- Excel Version: Office 365
- Location: 37 East 18th Street New York
- Contact:
Re: TM1 Slice data does not match cube data
The only time I have seen this is when we had a problem with security. If I remember rightly we reset security and restarted the server. (Just incase)
Struggling through the quagmire of life to reach the other side of who knows where.
Shop at Amazon
Jimbo PC Builds on YouTube
OS: Mac OS 11 PA Version: 2.0.7
Shop at Amazon
Jimbo PC Builds on YouTube
OS: Mac OS 11 PA Version: 2.0.7
- stephen waters
- MVP
- Posts: 324
- Joined: Mon Jun 30, 2008 12:59 pm
- OLAP Product: TM1
- Version: 10_2_2
- Excel Version: Excel 2010
Re: TM1 Slice data does not match cube data
Which sub-version of 9.4.1 are you on? I had a similar problem with, (if I recall correctly) 9.4.1 MR1 FP2, when selecting say month June, the slice was showig month July.
I went back to MR1 until the FP3 came out. I think FP2 HF16 aslo cured it.
I went back to MR1 until the FP3 came out. I think FP2 HF16 aslo cured it.
-
- Posts: 2
- Joined: Wed Jun 23, 2010 12:48 am
- OLAP Product: TM1
- Version: 9.4.1
- Excel Version: 2003
- Location: Sydney, Australia
Re: TM1 Slice data does not match cube data
Thanks everyone - turns out this was an issue with FP2. We resolved by uninstalling TM1 from all computers affected, then reinstalling FP1 only which seems to have solved the issue