Many TM1 users have cubes with rules associated with historical data or completed plan versions and are needlessly recalculating their data on a continuous basis. This creates an unnecessary performance drain, and to make matters worse, what happens when the business rules change? Do you change history? Do you make rules overly complex by adding a time or version component to all of your rules? Using a few simple steps, this data could be “frozen” or made static, resulting in faster response time, less RAM consumption, and alleviating issues when business rules change. In this article, we will explain how to go about freezing this data. Read more