Category Archives: Turbo Integrator
The AttrClear or ClearAttr function doesn’t exist in TM1. Here is an easy method to replicate what functions like these would do, with a downloadable example
The YEAR function in TM1 allows us to extract the number representing the Year from a date. Here we explain it’s syntax and give an example combining it with the DATE function.
Virtual Dimensions in TM1 and Planning Analytics allow you to use Attributes to create additional analytic capability. Here we explain how to create them with code examples.
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.
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.
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.
The MONTH function in TM1 allows us to extract the number representing the Month from a date. Here we explain it’s syntax and give an example combining it with the DATE function.
Here is a really easy method for checking if an Attribute Exists in TM1 via Turbo Integrator process. It essentially does what an “AttributeExists” or an “AttrExists” function would do for you if they existed in TM1.