TM1 Forum

For future readers: This is a IBM bug (link to IBM APAR) for which there is a fix available in 2.0.8 and higher.

Awesome!!!
We have exactly this situation in the past, and will give this a try next time.
@paulsimon You are THE MAN!

Proof that this community and forum rocks!

Assuming that your production and UAT instance have different names, you could get a number of problems: 1) Each application file would be hard-coded to a specific server name. Opening this file on a TM1web associated to a different TM1 instance name would not work.The servername within the file wou...

Hi, I am a long time user of vizier and I have to say that it is bloody awesome as a TI editor. It has many features, but mainly use it for is TI editing and hot promoting between servers. At their recent Sydney User conference, Cubewise gave us a sneak peak at the "in-the-labs / coming soon&qu...

Hi, As another option (and in my mind a superior one) we now use java to calculate our IRRs. We trialed these rules and a cube/TI combination option and the java results are 100% accurate to excel, and blisteringly fast, compared to other alternatives So, we now have a TI process that generates the ...

Awesome ardi!

We had not seen/suspected this behaviour, and could not for the life of us reproduce the hang.
Really looking forward to reproducing the issue using your instructions and adding our voice to IBM to get this fixed properly.

Thanks

Yes! We are also dealing with this beast. Running TM1 10.2.2 and we sporadically will have the entire TM1 instance hang when a user presses UNDO on a websheet. It is not every time UNDO is pressed, only sometimes. No matter what we (admins) do, we have not been able to replicate the issue, even logg...

You can get MTQ to "work" in a TI by using the 'ViewConstruct' TI Function to build your TI view (and thus use MTQ) Check out the following blog post for a good summary of MTQ for 10.2 where this is shown at the end. http://cubewise.com/blog/ibm-cognos-tm1-multi-threaded-queries-mtq-tm1-102

Wim, I've had to exactly as you describe for the same reasons. The only additional step you need to do is to make your active form against the }ElementAttributes cube of your temporary dimension. The MID functions (or DBRAs) could then split out your individual dimension elements, which could be use...

You can see from the screenshot that Mike supplied, that the values for button properties like 'getLabel' and 'getScreenTip' are all determined by calls to the "tm1p.xla!RibbonGetLabelCall" Given that the button names and tip-text never change, I have found that hard coding this in the rib...

This issue is only apparent when using TM1 with a keyboard with a number pad (ie not a laptop keyboard) One way that I have used to get around this was to use the following VBA code. This checks if the Numlock button is off, and turns it back on if needed. (Usual caveats of use at your own risk etc)...

The TM1 ribbon is constantly chatting to the tm1p.xla to get things like button text and enabled/visible state, every time you move around the spreadsheet (as it checks (for instance) if that cell is in an Active Form or not). This causes navigation delays as well as the horrid symptoms you describe...

Hi,
Try the following syntax in the SQL:
Where variablename is either a TI process parameter, or any other variable defined in the prolog tab (in your case via a TIMST function)

I have seen the same in an environment that was also citrix deployed (noted from your footer). When connected to the 9.5.1 server via 9.5.1 perspectives in a citrix excel session, selecting the Transaction Log did nothing. When connected to the same server via a local excel session, it worked fine. ...

Have a look here

Have you tried to use a consolidated element instead of adding them up within the MDX? ie

When creating reports that need to move through the Dev > Test > Production server migration, one accepted easy method is to create a small hidden table listing the known possible servers, with a =TM1User(<servername>) formula next to them. If the user opens the report and is logged into any of thes...

I would suggest that you are still getting tripped up by the deleted elements screwing with your DNEXT function. You could cycle through the dimension, checking for matching attributes, and insert these into a temp dimension. Then cycle through the elements in this temp dim, and delete each of those...

I would create a new element [GL Account] . [Auction Year Month], and a rule that would combine [Auction Year] and [Auction Month].
eg if [Auction Year] = 2011 and [Auction Month] = 09, then [Auction Year Month] = 201109

Then use [Auction Year Month] in the MDX sorting.

I use the worksheet function: TM1User("ServerName"). If it returns a blank - then they are not connected.
Though I am not sure in what version this function was introduced (I am using TM19.5.1)