Renaming the element name – SwapAliasWithPrincipalName
In Realtime Scenarios, sometimes we get the requirement to correct/update the Principal element name(s) in a Dimension. This would relatively be easy if the dimension is being used in one cube. In case where the dimension is used in multiple cubes, updating element name(s) without affecting the data of all the cubes, is a bit challenging. Either we export data of the cube and change the element name(s), then import the data and validate cube before and after the element change. Or deploy the Bedrock process, which requires the reboot of Instance.
I recently came across a problem statement at a client site and thought it would make good content to share for my blog article so without further ado here it goes...
Gone days, where we had no control/alerts mechanism on the TM1 database, CPU/memory it consumes, react at the nick of the moment before TM1 server crashes.
As you plan to adopt IBM Planning Analytics cloud, it’s important to understand what it takes. This blog highlights areas you will be involved-in when you upgrade from on-premise TM1 10.x.x to Planning Analytics on Cloud.
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!