DimensionElementDelete Function TM1: Syntax and Use

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!

This entry was posted in TI Functions and tagged DIMENSIONELEMENTCOMPONENTDELETE, DimensionElementDelete, DimensionElementInsert, dimix, IF. Bookmark the permalink. | Tagged DIMENSIONELEMENTCOMPONENTDELETE, DimensionElementDelete, DimensionElementInsert, dimix, IF | 1 Comment

CubeSetLogChanges TM1 function: Syntax and Example

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.

This entry was posted in Logging, TI Functions and tagged CubeSetLogChanges, Transaction Log. Bookmark the permalink. | Tagged CubeSetLogChanges, Transaction Log | Leave a comment

CreateHierarchyByAttribute Function in TM1: Syntax and Use

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.

This entry was posted in Attributes, TI Functions and tagged CreateHierarchyByAttribute, HierarchyDestroy, HierarchyExists. Bookmark the permalink. | Tagged CreateHierarchyByAttribute, HierarchyDestroy, HierarchyExists | Leave a comment

Who Changed that TM1 Data? Using the TM1 Transaction Log

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!

This entry was posted in Logging, TM1 Admin and tagged logging, Transaction Log. Bookmark the permalink. | Tagged logging, Transaction Log | Leave a comment

Over Feeding in TM1 – What is it and How to Avoid it

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.

This entry was posted in Feeders, Performance and tagged Feeders, Overfeeding, Rules. Bookmark the permalink. | Tagged Feeders, Overfeeding, Rules | Leave a comment

How to Take a Snapshot in Planning Analytics for Excel

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.

This entry was posted in Planning Analytics Excel and tagged PAX, Planning Analytics for Excel, snapshot. Bookmark the permalink. | Tagged PAX, Planning Analytics for Excel, snapshot | Leave a comment

DType Function in TM1: Syntax and Use

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 entry was posted in Rule Functions, TI Functions and tagged CellIncrementN, CellPutN, CellPutS, DType. Bookmark the permalink. | Tagged CellIncrementN, CellPutN, CellPutS, DType | Leave a comment

How to Change TM1 to use Cognos Security (CAM)

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.

This entry was posted in Cognos BI, Configuration, Installation, Security and tagged bi interop, CAM Security, planning.html, pmhub.html, Security, TM1p.ini, tm1s.cfg, tm1web.html. Bookmark the permalink. | Tagged bi interop, CAM Security, planning.html, pmhub.html, Security, TM1p.ini, tm1s.cfg, tm1web.html | Leave a comment

Enabling TM1 Rules via a Control Cube

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.

This entry was posted in Rule Management, Rules and tagged continue, performance, stet. Bookmark the permalink. | Tagged continue, performance, stet | Leave a comment

Cascading Element Level Security in TM1

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.

This entry was posted in Security, TI Coding, TM1 Admin, TM1 Administration, Turbo Integrator and tagged CAM Security, element level security, Element Security, Security. Bookmark the permalink. | Tagged CAM Security, element level security, Element Security, Security | 1 Comment