TM1 10.2 Security Changes

With TM1 10.2 security changes, TM1 10.2 now allows you to share/re-use the same dimension in multiple approval applications.  This is a nice feature, since it eliminates the need to maintain a duplicate dimension.  With that being said, there are changes to how security is structured and managed in this new version.  Please review the documentation in the link provided, as there will be changes automatically generated to models upgraded from versions prior to 10.2.

If you have additional questions regarding security in TM1 10.2 please reach out to us at  We have a fantastic services team ready to answer all of your questions.  Also if you have not joined our community yet, what are you waiting for?  Go to and join today!  it takes less than 1 min and you will ensure that you are among the first to know about how new programs and blogs.

Saving TM1 rules takes too long!

“What's the deal with the TM1 rules I'm writing?!?!” Why does saving TM1 rules take a long time occasionally?

I just recently created a TM1 rule that took over 5 minutes to save.  I double-checked my feeders and couldn’t find a problem with them and my totals were looking correct at the consolidated levels as well.

While reviewing my cube, I saw that the account rows in a P&L cube were not showing the rows that required a % properly.  After a little poking around, I realized that I had formatting on my measures dimension, as well as, my variance dimension.  The two were conflicting with each other and not showing the % rows correctly.

After I removed the formatting on the correct variance dimension elements, which fixed that problem, I then noticed my rule would now save in one second.

Apparently, conflicting formatting can cause performance issues with TM1 rules. For more specific questions regarding TM1, do not hesitate to contact us at

Have you joined the Lodestar community yet?  If you haven't, what are you waiting for?  Just go to and sign up day.  It takes less than 1 minute and will ensure that you are up to date on all new programs and blogs.

TM1 Implementation Methodology for Success

All Cognos TM1 implementations require a strategy to deliver an appropriate reporting solution. This is the plan that will ensure that each business user will have access to all the TM1 data they need, in the most usable format and in a timely manner. This plan must be based upon environmental configurations, user experience levels, as well as time and budget constraints. The plan should outline a strategy that will meet the business requirements during acceptance testing, initial deployment to production, as well for a conceivable period of time into the future.

A proven, best practice strategy for reporting is to Solve, then Evolve.

Screen Shot 2013-09-16 at 9.16.53 PM

With this approach, the application’s “core statement” needs are first identified and then “solved for”. These are not individual analyst support reports or ad hoc data queries; rather, only those reports required to complete (close) and/or monitor a business process (P&L, Income Statement, Balance Sheet, etc.). The reports may also include critical KPI’s or KRI’s. They are usually fixed in format and require a standardized styling format. They may be parameter-driven; for example “Income Statement” by period, or by country. These reports lend themselves best to being deployed using TM1 Websheets.

Once the standard “book of business” statement reports have been delivered, ancillary statistical reporting needs can then be considered. These reporting needs are usually much more individualized and narrowly focused. These would include very specific views of data based upon specific business questions. They can include “check” and “reconciliation” views of data. These reports are almost always solvable using TM1 compiled cube views that are accessible using TM1 Web and the TM1 CubeViewer. The TM1 CubeViewer will also allow users to perform various filtering and drilling operations on the data that each cube view displays.

Finally, as the application matures and the level of user experience increases, it may be beneficial to evolve the reporting solution by considering the deployment of TM1 Perspectives to specific members of the business user community. These users will usually be the “power users” of the group with responsibility for performing more in depth, advanced or complicated analysis and reporting. Because of the nature of TM1 Perspectives, it is recommended that care be taken before offering Perspectives as a user option. Performance and concurrency are the 2 main areas that may have a detrimental effect on both the Perspectives user as well as the overall TM1 application.  TM1 provides a layer of security that you can apply so that these “power users” can create TM1 WebSheets for input and reporting purposes, yet are locked out from actually creating/editing TM1 objects (i.e., Cubes, Dimensions, etc).

Bulk Absorption and Configuration

From a pure architectural perspective, what is sometimes referred to as “bulk uploading”, sometimes is (mistakenly) considered to be part of reporting or included in the data consumption component of the application.  Loading and/or updating data is part of the applications absorption or configurations components and should be handled with a best practice approach of leveraging TM1 TurboIntegrator scripts and/or active Websheets (designed based upon user and environmental requirements and constraints).


It is important to keep the implementation of the reporting solution (the consumption layer) separate and distinct from the key value add (the processing) of the TM1 application being deployed. From an architectural perspective, the manner of consuming the application’s data may (and most likely) will evolve:

  • As user needs and levels of expertise change, the method for consuming data may need to change
  • Other reporting tools and/or technologies may be considered in the future (for example, Cognos Insight or Cognos BI) which will change the method for data consumption
  • Organizational changes may require additional or different analysis and reporting; and, therefore, may change the method of data consumption.

By solving the initial reporting requirements, you are able to provide a timely deliverable that will be a gateway to user acceptance and product satisfaction, as well as management appreciation of the ROI for this software investment.   Keep in mind too, that properly training users goes a long way.  The more they understand the usefulness of TM1 and how it can fulfill their needs, the better they will assist in providing requirements for future evolution.