Hi all,
I am trying to open a specified view and then set a new title element for a specified dimension. Below, you can see the syntax I use.
http://fully.qualified.domain.name.com:9510/tm1web/TM1WebCubeViewer.jsp?CubeName=CubeName&CubeViewName=ViewName&ServerName=ServerName&HostName=HostName&AccessType=PUBLIC&Title_Year=2015
The url always opens the view successfully. However, it sometimes set the title element, and sometimes doesn't. When it cannot set the title element, TM1Web freezes and you need to re-open the browser to continue to use TM1Web.
I tried the same url syntax in different cubes. For a relatively small cube, I tried few times and it always worked. For a relatively larger cube, I tried many times and it only worked few times and didn't work the other times. So, this might have something to do with size, number of dimensions, or other features of the cubes; however, I do not have further proof to conclude that this is the case.
Has anyone of you experienced the same/a similar situation? What are your ideas about the possible cause of the problem/how to solve it?
Thanks,
TM1 10.2 URL API | Problem with title setting
-
- MVP
- Posts: 1828
- Joined: Mon Dec 05, 2011 11:51 am
- OLAP Product: Cognos TM1
- Version: PA2.0 and most of the old ones
- Excel Version: All of em
- Location: Manchester, United Kingdom
- Contact:
Re: TM1 10.2 URL API | Problem with title setting
What are the element names that cause it to fail?
I always make sure to only pass principle names as have found that special characters or spaces that may exist in an alias for obvious reasons can disrupt a URL.
I always make sure to only pass principle names as have found that special characters or spaces that may exist in an alias for obvious reasons can disrupt a URL.
Declan Rodger
-
- Posts: 25
- Joined: Wed Nov 12, 2014 2:27 pm
- OLAP Product: TM1 + BI
- Version: 10.2 10.2.2 + 10.2.1 10.2.2
- Excel Version: 2010 32 bit
Re: TM1 10.2 URL API | Problem with title setting
Hi declanr,declanr wrote:I always make sure to only pass principle names as have found that special characters or spaces that may exist in an alias for obvious reasons can disrupt a URL.
The elements I pass are "2015", "2014" etc. without any special characters.