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.
The nearly unlimited flexibility of Excel is powerful, but also one of the biggest cause of concern. How can you trust that a workbook shows the latest information, is built on trusted source data and does not containing any modelling errors? Any attempt to manage these risks is hampered by the fact that sheets can be added to a workbook, formulas can be changed and copies of the workbook can be easily created.
Despite how obvious the benefits of the functional database seemed to me when I invented TM1 over 30 years ago, I have learned that these benefits are not immediately obvious to most people.