Thank you if you have come back for more! Hope our last blogs of this series Unravelling TM1 : Lesser Known Facets – Part A & Part B were meaningful. In this part we will unearth & explore few more of these lesser known gems.
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.
Often times, when we as a developer are loading the data from a particular source and intend to create a view to debug the data for analysis and troubleshooting, typically we do it by creating the view and subsets and assigning the subsets to the view in Prolog tab.
As per the IBM’s guidelines, the following points must be taken into considerations pertaining to Planning Analytics on Cloud.
- The tm1s.cfg file must exist in the base directory
- Any folders that you create must be below the base directory
- The location or the name of the base directory cannot be changed
- The existing tm1s.cfg file must not be replaced from another server.
Sandbox, also known as Personal Workspace is your personal work area where you can edit the data values as many times as you want and keep the changed data separate from the base data.
Sandboxes and Personal Workspaces are private to each user and cannot be seen by other users. Your data values are viewable to others only when you commit them back to the base data. A Personal Workspace is a special, default sandbox that is unnamed and always where you work if that capability is turned on.
In TM1 rules, an alias could be used in defining the target area (area definition), within rule calculation as well as in Feeders.
However, few things must be kept in mind when using Alias in the Area definition of the cube.
- As the rule is now using the attribute value to dictate the rule calculations, it adds a potential risk of inadvertently updating the alias by the users thereby resulting in incorrect calculations. This could be mitigated by applying security on control objects.