Tag: Planning Analytics
People might not generally be aware that in Planning Analytics (TM1 server v11) virtually all server configuration parameters are now dynamic, meaning they can be changed with immediate effect while the server is in session. This includes IntegratedSecurityMode which affects how users are able to log in.
This presents an easy way to prevent users establishing new sessions and interfering with batch load processes. Just change the IntegratedSecurityMode parameter and users won’t be able to log in. No need to for a TI to remove client/group associations or change all passwords which then need to be put back again.
Naming conventions are necessary both for end users and developers to make any system understandable and navigable. Deciding on a naming convention is a critical step and there are many opinions on what the "best" convention may (or may not) be. The rules and content of any naming convention actually matter far less than whether the conventions are consistently and universally applied within a given system.
Although naming conventions may be open for debate what isn't is that all naming conventions must avoid illegal characters and reserved words. This is a founding principal of any naming convention. To find out more about what this means in the context of Planning Analytics (TM1) read the article in full.
First of all, Planning Analytics is just a new name for TM1.
Over the last few months, a number of customers have started planning the upgrade to Planning Analytics Local. There seems to be the perception that this process is more complicated than any other upgrade done before with TM1. In this article, I try to bust some myths and provide the information for your upgrade.