Release notes are getting longer with every version. Version 3.1.12 of IBM Planning Analytics includes over a dozen changes. For a TM1 team that manages budget cycles, forecasts, and monthly closings simultaneously, one question is crucial: Which of these changes will actually impact my day-to-day work? We’ve identified the most important features. The result: four new features that are specifically relevant to most TM1 users in the DACH region.
What’s behind IBM Planning Analytics 3.1.12?
IBM Planning Analytics is IBM’s integrated enterprise planning platform, built on TM1 as its in-memory calculation engine. Version 3.1.12 follows the monthly release cycle that IBM has established for Planning Analytics as a Service and Certified Containers.
For on-premises installations, version 3.1.12 is available as a Technical Preview. This means it is suitable for test environments but not yet for production use. IBM typically releases on-premises versions as stable releases via IBM Fix Central a few weeks after the SaaS release.
What makes version 3.1.12 special? Instead of individual bug fixes, this release includes several feature packages, each of which is of interest to different user roles: administrators, modelers, and power users will benefit from new features.
Which four features change your day-to-day work?
Dependency Graph: your model at a glance, at last
Anyone who manages a TM1 model that has grown over time knows the problem. If I change this dimension, which cubes are affected? If I delete this process, which chores depend on it? Until now, answering such questions meant digging through the database manually.
3.1.12 introduces the Dependency Graph in Planning Analytics Workspace. When you open a model, you can see at a glance how cubes, dimensions, TurboIntegrator processes, chores, and control structures are linked to one another. Three use cases that provide immediate value:
- Impact analysis before a change: Before you edit a process, you see exactly what depends on it.
- Troubleshooting: Follow the dependency path to find the root cause of a problem faster.
- Onboarding: New team members understand the model structure without having to ask a lot of questions.
You can export the graph as an SVG, for example, for the system documentation or audits.
REST APIs for user and group management: no more manual user administration
Starting with 3.1.12, users and groups in Planning Analytics Workspace can be managed entirely via REST APIs: create, change, delete, set group memberships, run bulk operations, filter, sort, paginate.
That sounds technical. The benefit is clear: In larger environments where users come from an Active Directory or a central identity system, admins can automate management. No more manual clicking through the Workspace interface when onboarding 50 new employees into a Planning project.
For teams that use Planning Analytics in conjunction with automation tools, this opens up new possibilities for custom scripts and integrations.
Calculations directly in the Cube Viewer: more flexibility for power users
Until now, you needed MDX or specific views to display your own calculations in Planning Analytics. With version 3.1.12, a Calculation menu is now available directly in the Cube Viewer. This allows you to create, edit, and remove calculations without having to go through the modeling tools:
- Member Calculations: Custom calculated members based on existing dimension members
- Set Calculations: calculations across sets
- Summary Calculations: aggregations and totals
- Custom MDX Expressions: direct MDX input for experienced users
Important for practical application: These calculations apply per view and per user; they do not constitute a permanent change to the model. This gives power users flexibility for ad hoc analyses, without altering the model structure.
SAP OData as a new data source: relevant for SAP environments
In 3.1.12, IBM adds SAP OData and Cognos Analytics to the list of supported data sources. For companies in the DACH region that run SAP as their ERP system, this is a relevant extension.
The Guided Import feature can now access SAP data directly, without the need for a separate ETL process or a TurboIntegrator script. This simplifies the initial loading of Planning models and makes it easier to regularly update master and transaction data from SAP.
Do you use SAP and Planning Analytics side by side?
We’ll show you how data integration can be made easier with version 3.1.12.
What steps should you take for your TM1 upgrade?
Upgrading to 3.1.12 is not mandatory. But having a clear plan helps you make the right decisions.
- First, decide whether you are running SaaS, Certified Containers, or On-Premises. On-Premises customers will receive version 3.1.12 as a Technical Preview, which means it does not include production support. If you need stable production environments, wait for the General Availability release.
- Check which of the new features are relevant to your setup. The dependency graph is immediately useful if you have a complex model with many dependencies. The user management APIs are worth using if you manage more than 20 users and want to automate that process.
- Test in a sandbox environment before deploying to production. Even though IBM tests its releases extensively, customizations such as TurboIntegrator processes or your own Rules may be affected by version changes in the TM1 server.
- Use the dependency graph for your own documentation. Before upgrading, this is a good opportunity to visualize the model structure and prepare it for internal handoffs or audits.
Why BI2run supports you with upgrades
We have been supporting TM1 and Planning Analytics projects in the DACH region for many years. When it comes to upgrades, we know from experience that the update itself is often the smaller part of the process. The real work lies in understanding which custom logic in your model is affected by version changes and how you can effectively integrate new features—such as the Dependency Graph or the REST APIs—into your existing processes.
If you’re unsure whether 3.1.12 is right for your setup or when it makes sense to upgrade, a quick conversation will clear things up. We’ll also be honest with you if now isn’t the right time.
Facts about IBM Planning Analytics 3.1.12
Glossary
Frequently asked questions about IBM Planning Analytics 3.1.12
What’s new in IBM Planning Analytics 3.1.12?
IBM Planning Analytics 3.1.12 introduces four key new features: the Dependency Graph for visual model analysis in Planning Analytics Workspace, REST APIs for automated user and group management, expanded calculation capabilities directly in the Cube Viewer, and SAP OData as a new data source. In addition, there are minor enhancements in the areas of Websheets, plans, and administration.
When will IBM Planning Analytics 3.1.12 be available for on-premises deployment?
As of the publication of this article, version 3.1.12 is available as a Technical Preview for on-premises deployments. This means it is suitable for test environments but not yet for production use. IBM typically releases the on-premises versions as stable releases via IBM Fix Central a few weeks after the SaaS release.
Is it worth upgrading to 3.1.12 right away?
That depends on your deployment scenario. For SaaS and Certified Container customers, the update runs automatically or with minimal advance notice. On-premises customers should use the Technical Preview for testing and wait for the GA version before upgrading to a production environment. Testing in a sandbox environment is mandatory, especially if you have custom TI processes or your own rules.
How exactly does the dependency graph benefit my work?
The Dependency Graph eliminates the need to manually research dependencies between TM1 objects. You can see at a glance which cubes, dimensions, and processes depend on one another. This speeds up impact analyses before model changes, simplifies troubleshooting, and aids in system documentation.
How do the new REST APIs for user management work?
The new APIs make it possible to programmatically manage users and groups in Planning Analytics Workspace: create, modify, delete, set group memberships, and perform bulk operations. This is particularly useful for larger teams that want to automatically synchronize user data from a directory system such as Active Directory.
What does “Technical Preview” mean in IBM Planning Analytics?
A Technical Preview is a pre-release version that IBM makes available to on-premises customers for testing. There is no official IBM support for this version, and it is not suitable for production environments. Please direct feedback and questions to the IBM TechXchange Community. Technical Previews give on-premises customers the opportunity to familiarize themselves with new features early on.
