Thank you if you have come back for more! Hope our last blog Unraveling TM1 : Lesser Known Facets – Part A was meaningful. In this part we will unearth & explore few more of these lesser known gems.
No matter how much we think we know about TM1, there are always these set of conditions that make you think “what-if there was a better way”??!! For example, not having to write a bunch of codes just to delete the subsets after using it in a Source View Or not writing the same area definition twice. What-if this could be done with less or no coding at all!
I want to keep this blog very simple so that people who do not know the concept of blockchain can understand it. Target audience – anyone who can read English.
In TM1, if a TM1 Cube has huge of volume of data and rule calculation, there is possibility that TM1 takes longer time to open a cube view, to look at the issue with performance would be TM1 View Caches (Stargate Views).
In this blog, let me explain you about one of the hidden/unused feature from IBM Cognos TM1.
One of the major challenges of promoting code to successive instances is packaging the code for promotion and finding a slot for downtime. Not to mention the sequence of steps required to carry out the procedures and to communicate to one and all about the impending downtime. Adding to this difficulty is finding downtime when users are accessing the application from across the globe.So irrespective of deployment size, either major or minor, the deployment process is never going to be easy. However you can potentially overcome this using one of the TM1 Suite tools.