To prevent the TM1p.ini file getting overwritten everytime

[Samp]

Hi Experts,

I did some search with respect to the subjected topic, but as I couldn't find any relative answers, please let me post this question here.

I need to change some parameters at the TM1p.ini file located at %appdata%. But each time, when the client (Ex: Perspectives) closed after accessing any of the TM1 application, then this file also getting overwritten , which is resetting my added setting.

So do I need to make the changes everytime before accessing any of the TM1 server ?, which could be a weird idea.

And I dont want to make this file as Read-only, as that would prevent me connecting any other servers via perspectives.

Hence please let me know your thoughts, Thanks in advance.

[Elessar]

Hi,
You need to close all the Perspectives and Architect windows before changing the tm1p.ini.

[Alan Kirk]

I need to change some parameters at the TM1p.ini file located at %appdata%. But each time, when the client (Ex: Perspectives) closed after accessing any of the TM1 application, then this file also getting overwritten , which is resetting my added setting.

So do I need to make the changes everytime before accessing any of the TM1 server ?, which could be a weird idea.

What you do need to do is accept that this is exactly the way it was designed to work. It's Client/Perspectives/Architect's way of tracking user config changes during a session. (Admin host, window sizes, etc.) The only exception is PreviousAdminHosts which I've noticed can sometimes be a bit iffy.

However it will usually only change whatever the session user has changed, which may include whatever you changed prior to that. What exactly is this magic setting that you're trying to include?

[Samp]

You need to close all the Perspectives and Architect windows before changing the tm1p.ini.

Thanks Elessar. This doesnt help, but my issue is different, please see below that the file is getting overwritten every time.

What exactly is this magic setting that you're trying to include?

Thanks Alan for the quick response. The Magic setting , well , let me try to keep the long story short. Its to fix the Multi-level UNDO issue of Excel (If we are adding the TM1 Add-in, Excel's UNDO is working for only one level), hence I tried to use the setting "DisableWritebackonDisconnect" for fixing the issue. Although it worked, the ini file is getting overwritten every time, after connecting with any TM1 server and closing the client.

However it will usually only change whatever the session user has changed, which may include whatever you changed prior to that.

If this would be the case, it makes logical. But strangely, the file is getting overwritten every time, even if you are connecting to the same server again, and opening the same cube & closing the perspectives.

If thats the case, how the solutions provided in scenarios like this(http://www.tm1forum.com/viewtopic.php?t=7196) are feasible ?, are we expected to add these setting changes everytime after closing the client !!?

[Samp]

I contacted IBM support further and they could replicate this issue at their end as well. And they have agreed it as a defect and forwarded the issue to their Product team.