TM1 Forum

Hi All, I too now have a stack overflow :evil: I have added another year into our time dimension and have the error messsage of stackoverflow. Our model is pretty big, so how can I go about understanding which feeder(s) need splitting up like Steve suggested above, when my error message says: 356792...

Thanks Andy Key, that solution worked. I didn't realise that TM1 'ignored' spaces, so my actual coding would probably have worked fine. The problem is when searching a subset for *No Specicic I_*, as it didn't return any values for 2016 due to the different format. Thanks for all your replies. Kirk

Hello. Help please! I am trying to extend our time dimension by another year using a TI process developed for the purpose. Everything looked fine, until I looked at a metric named, No Specific I_YYYY_WWW. For the prior year (2015), the format is as expected, but for the year 2016 (the year I have ad...

Thanks for the replies, I feel much happier about this now.

Kirk

My organisation are looking at virtualising their server provision later in the year. Currently we have two standalone servers running 9.5.1, and a seperate Citirx provision that handles the client and remote access. I have spoken to IBM who have informed me that TM1 will operate on a virtual server...