Here is how to simply delete a single element from a dimension in TM1. Note DimensionElementDelete permanently deletes the element from the dimension and all associated data from any cube the dimension is used in – so please be careful!
When we run a Turbo Integrator process in TM1, the Transaction Log will normally have a record written for each data change. To speed up the TI, we can turn off transaction logging for a TI using the command CubeSetLogChanges.
Here is a great way to create virtual dimensions in TM1 based on attributes. These allow you to intersect multiple virtual dimensions from the same physical dimensions in a PAW or PAX report. Here we discuss the CreateHierarchyByAttribute function and give an example on how to use it.
Have you ever had an inexplicable change to TM1 data? You know, when a user comes to you and says, John (in my case), the data in TM1 has changed since I looked at it last month? Well, if you have, here is the solution. And it is really easy!
Overfeeding is where TM1 feeders are targetting more cells than are required. This can lead to excess memory consumption and reduce performance. Here we explain over feeding and how to avoid it.
Here is how to create a snapshot of a TM1 report in Planning Analytics for Excel – PAX. This essentially does a copy, paste special, values on the TM1 formulae only, leaving all your Excel formulae untouched. It is very useful for creating a version of a TM1 report that is disconnected from the underlying TM1 data.
Use, syntax and example of the DType function in TM1 and Planning Analytics. In this post we explain the use of the DType function and give an example of how it can be used to determine the cell type of a cube when loading data via a Turbo Integrator process.
This is a comprehensive guide to configuring TM1 to use Cognos CAM security. It includes why you might connect Cognos security to TM1, TM1 environment changes and how to deploy and configure the BI Interop files to your BI application and gateway servers.
A simple solution to enabling and disabling rules for different versions (or scenarios) using either an attribute on the Version dimension or a simple cube, intersecting the }Cube and Version dimensions.
Here we present a fully worked example of how to create element level security for an organisation that requires complete lockdown for entire branches of a dimension. It uses element level security down to the N level, applied via a TI.