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!
IBM has recently launched its Planning Analytics version 2.0.5 (on 25th June 2018); this article captures highlights of what’s new, improved and denounced.
One of the most neglected and least prioritised activity among the grand scheme of development, in my opinion, is applying correct formats to data, both in cubes as well as standard web reports. In all fairness, if you’re one of my kind (occasionally-fall-into-a-slack type) who often miss out on this detail, then you have arrived at the right place. In my defence, I still feel that given the number of data points that one must apply formatting, it is only natural to miss a few, which then gets picked by business in live environment.
While working for a particular client project, I was asked to review an existing long running Turbo Integrator (TI) process and find out ways to optimise its processing time, without compromising on the business functionality.
Most who are still on Cognos Business Intelligence software version 10.2.x would know that the software version was due End of Service this April 2018. It was quite dreading for existing users who had not planned an upgrade to Cognos Analytics (or C11 as it is called within IBM) just yet as it wasn’t really a straight forward version upgrade but a complete overhaul in the way you would interact with Cognos BI; more intuitive, user friendly and insightful but requires a bit of learning and a little more unlearning.