TM1 Forum

Hello experts!

Just curious if anyone has encountered this TM1 10.2 always asking to save an untouched TI process before closing it?
We had existing TIs from our separate server which is 10.1.1. I copied some and tried to do my dev in my new server but I noticed that behavior. I thought maybe it was just because I copied the process that is previously 10.1.1 and opened it to 10.2, But no. I tried to create a new process in this 10.2 using a database table as a source but the behavior still exists. I also tried in the samples provided in the install.

Can anyone shed some light? Thanks in advance.

I see this as well, very annoying. I don't know what the reason is but I blame Performance Modeler! (joking, but it sounds good, isn't it? )

I would blame Performance Muddler as well. After running a training course on it last week I can confirm (based on delegate feedback) that it is the root of all evil!!!

Yeeehaa!!!

Thanks Wim and Jim. I thought it's only ours. I think I'll just ask the IBM support regarding this.

Thanks.

I also have this on 10.1.1 FP1; the model is not even added to the TM1 Application Web, it does not seem to be related to PM

I'd still blame PM as we've already established it's to blame for everything.

If already this topic: I recently experienced that opening a TI process from Architect takes ca. 30 secs (working remotely on the server) and I think it happens since we added the terminal server role in addition to the application server, however it is rather just a feeling that adding the terminal server role and the long time opening the TI are in correlation.
Has anyone seen this before?

Version 10.1.1 FP1.

Thanks
Matyas

jim wood wrote:I'd still blame PM as we've already established it's to blame for everything.

Personally I tend to blame what it's written in, not just how it's written.

Because that way I cover both Insight and the Applications Portal, too...

mvaspal wrote:If already this topic: I recently experienced that opening a TI process from Architect takes ca. 30 secs (working remotely on the server) and I think it happens since we added the terminal server role in addition to the application server, however it is rather just a feeling that adding the terminal server role and the long time opening the TI are in correlation.
Has anyone seen this before?

Version 10.1.1 FP1.

No, but I think the key pieces of missing information are... what's the data source? Have you modified it? If it's ODBC how long does it take to open the query using something like the Microsoft Query tool? If it's a text file has the size of the file changed.

Stuff like 'dat.

Alan Kirk wrote:

jim wood wrote:I'd still blame PM as we've already established it's to blame for everything.

Personally I tend to blame what it's written in, not just how it's written.

Because that way I cover both Insight and the Applications Portal, too...

Where's the like button, where is it, oh wrong site....

sorry, my language was misleading, this is for ALL processes, independently from the data source. A simple SaveDataAll process also opens in 30 sec.