Slow Report Performance After Upgrade to TM1 10.1.1
-
- Posts: 4
- Joined: Wed Feb 22, 2012 2:34 am
- OLAP Product: TM1
- Version: 10.1.1
- Excel Version: 2010
Slow Report Performance After Upgrade to TM1 10.1.1
We are currently currently running TM1 9.5.2 using Excel 2007 in our Production Environment. We have just upgraded our Dev environmnet to Excel 2010 and TM1 10.1.1 FP1. We are finding that when we refresh the Dev environment with the data from production, for some reports, it takes a long time to open in TM1 10.1.1 Perspective. This happens consistently to same report(s). We found a workaround by reuploading the same report back to the Dev TM1 10.1.1 environment. Thereafter, the issue goes away. Has anyone experience this problem. Is there a solution, other than our workaround?
- macsir
- MVP
- Posts: 785
- Joined: Wed May 30, 2012 6:50 am
- OLAP Product: TM1
- Version: PAL 2.0.9
- Excel Version: Office 365
- Contact:
Re: Slow Report Performance After Upgrade to TM1 10.1.1
Nope, you mean the excel files in TM1? Pending on opening only? How about the refreshing speed?
-
- Posts: 4
- Joined: Wed Feb 22, 2012 2:34 am
- OLAP Product: TM1
- Version: 10.1.1
- Excel Version: 2010
Re: Slow Report Performance After Upgrade to TM1 10.1.1
Its slow on both opening and refreshing. It take around 10 minutes to open, when it normally opens in 30 seconds in our Production environment running TM1 9.5.2.
-
- Posts: 4
- Joined: Wed Feb 22, 2012 2:34 am
- OLAP Product: TM1
- Version: 10.1.1
- Excel Version: 2010
Re: Slow Report Performance After Upgrade to TM1 10.1.1
Just spoke to IBM, and it seems like others are having similar issue. They are on Excel 2010. I wonder if this an issue with Excel 2010 compatiblity with TM1?
-
- Community Contributor
- Posts: 349
- Joined: Tue Aug 17, 2010 6:31 am
- OLAP Product: Planning Analytics
- Version: 2.0.5
- Excel Version: 2016
Re: Slow Report Performance After Upgrade to TM1 10.1.1
We have had issues on this setup where changes would be made to websheets and then we update them on the server. Then they spin and spin untill operation failed. The fix is to delete the websheet and then upload it.