Category: Blog
-
Downloading elements during the documentation
By default, Pulse is going to download the elements for all dimensions with fewer elements than the maximum number of elements defined in Pulse.cfg (MaximumElements). If you don’t need Pulse to download elements, you should turn this off. By turning this off, the documentation will be significantly faster because Pulse will not have to request…
-
Determine the version of IBM Planning Analytics
Updated on the Nov,2nd 2022
-
Cube Viewer and Subset Editor Hidden Gems
Arc continues to establish itself as a well know state of the art development interface for IBM Planning Analytics (TM1) developers.
-
Arc and Slice v4.0 is now available
A new version of Arc and Slice is now available to download. Version 4 is a big milestone in the history of Arc and Slice. You can now connect your Arc server to Pulse to unlock many new features in your Arc application, such as Instance/Server Monitoring, Full Model Search, Alerts and Change Tracking. We…
-
Pulse v6.2 is now available
Pulse v6.2 comes with many optimizations in the logic to determine the status of the TM1 instances. The main new feature is the connection with Arc.
-
Create Dynamic Asynchronous Views with MDX
Everyone who works with IBM Planning Analytics / TM1 is familiar with a cube view that you can create using a cube viewer.
-
Making it Easier to Write and Test MDX Queries with Arc
As we explained in a previous article, MDX is becoming more and more important in the IBM Planning Analytics / TM1 community and it is one of the key skills that any TM1 developer needs to have in order to make the most of the software.
-
How to Get the Most out of MDX Forms with Slice
MDX forms are an incredibly powerful add-on to the existing Excel reports in IBM Planning Analytics (TM1) and they offer a tremendous level of flexibility and customization to get you the results that you need. In this article, we’re going to go deeper into some of the more advanced use cases, so if you’d like…
-
Applying your own naming conventions for parameters and variables in Arc
Process naming is used by Arc when adding prefixes to new parameters and variables. It is also used for matching variables against dimension in CELLGET and CELLPUT functions. For example a variable called vAccount will automatically be inserted into a CELLGET (using auto-complete) if it has a dimension named Account.
-
Pulse Transforms Cold Migration in TM1
We’ve all had that moment where we complete a migration of IBM Planning Analytics (TM1) objects and then when we start the TM1 instance, we realize that we forgot a dimension, an attribute cube, or a picklist cube. This can be very frustrating as it means that you have to stop everything and restart the…