RIGHT TM1 Function: Use and Syntax

The RIGHT function from Excel does not exist in TM1. We need to use a combination of SUBST and LONG functions instead. Where you have a formula in Excel in A2 that is = LEFT ( A1, 4), where the contents of A1 is the string “ExploringTM1”, the formula will return the first 4 characters, i.e. “Expl”. To achieve the same result in a TM1 Turbo Integrator process we need to … Continue Reading

This entry was posted in Rule Functions, TI Functions. Bookmark the permalink. | Leave a comment

LONG TM1 Function: Syntax and Use

The LONG function in TM1 returns the length of a string as a value.  It is similar to the LEN functions available in both Excel and SQL Server. Syntax of LONG The syntax is LONG(string); where string is either the literal string to be evaluated or a variable that contains the string to be evaluated. Use An example of the use of it is as follows sString = ‘ExploringTM1’; LONG ( sString ); will return … Continue Reading

This entry was posted in Rule Functions, TI Functions and tagged LEN, LONG, SubSt. Bookmark the permalink. | Tagged LEN, LONG, SubSt | Leave a comment

LEFT TM1 Function: Use and Syntax

The LEFT function from Excel does not exist in TM1. We need to use SUBST instead. Where you have a formula in Excel in A2 that is = LEFT ( A1, 4), where the contents of A1 is the string “ExploringTM1”, the formula will return the first 4 characters, i.e. “Expl”. To achieve the same result in a TM1 Turbo Integrator process we need to use the SUBST function. A … Continue Reading

This entry was posted in Rule Functions, TI Functions. Bookmark the permalink. | Leave a comment

Limiting a Rule to Active Scenarios Only

Today I wanted to update a rule so that the processing of the rule was limited only to those scenarios that are “active”.  I could have gone through each line in the rules and added specific references to the scenarios I want to be active in the scope of each line of the rules. What I wanted was to limit rules to work only on specific scenarios. I then thought of this. If … Continue Reading

This entry was posted in Rule Examples, Rules. Bookmark the permalink. | Leave a comment

CubeClearData Syntax and Use

CubeClearData clears all of the data in a cube. It is a TurboIntegrator function, valid only in TurboIntegrator processes. This function is much faster than doing an operation such as creating a view to cover the entire cube, and then doing a ViewZeroOut() to zero out the entire cube, however it does not give you the flexibility to delete the data from a view or slice of a cube. When you use … Continue Reading

This entry was posted in TI Processes and tagged CubeClearData. Bookmark the permalink. | Tagged CubeClearData | Leave a comment

ATTRN TM1 Function: Use and Syntax within TI and Rules

ATTRN stands for ATTRibute Number, in other words it returns the contents of a string attribute from an element in a dimension in TM1. Syntax of ATTRN The syntax is ATTRN (dimension, element, attribute); where: dimension is the dimension you want to interrogate element is the element you want to find the attribute for attribute is the name of the attribute you want to get the result of Usage Assume that … Continue Reading

This entry was posted in Attributes, Rule Functions, TI Functions. Bookmark the permalink. | 1 Comment

DataSourceCubeView: Syntax, Use and Example

Another piece of the puzzle of setting up an AsciiOutput is to define a view and then export that view. Why would you do this?  Well, you can either go through a series of IF statements in your metadata or data tab checking each record to see if it satisfies a long list of criteria (e.g. if the Account is Sales and if the Scenario is Actual etc.), or you can … Continue Reading

This entry was posted in TI Functions and tagged ASCIIOUTPUT, DataSourceCubeView. Bookmark the permalink. | Tagged ASCIIOUTPUT, DataSourceCubeView | Leave a comment

Text File Export from TM1 – AsciiOutput Functions

When we are exporting from TM1 to a text file there is a set of functions we can set that modify the way the AsciiOutput process behaves.  These include: Suppress Rule Calculated values or not ViewExtractSkipRuleValuesSet Suppress Zero values or not ViewColumnSuppressZeroesSet Suppress Rollup, or Consolidation Calculated values or not ViewExtractSkipCalcsSet Set the datasource server name DatasourceNameForServer Set the datasource cube view DatasourceCubeView These can all be defined prior to starting an AsciiOutput to modify … Continue Reading

This entry was posted in TI Functions. Bookmark the permalink. | Leave a comment

ViewColumnSuppressZeroesSet

This is one of a set of functions that define the behaviour of a Turbo Integrator AsciiOutput. The ViewColumnSuppressZeroesSet function sets the output to either extract zero values values or not, depending if a flag is set (0 for export, 1 for skip). Syntax ofViewColumnSuppressZeroesSet ViewColumnSuppressZeroesSet(Cube, ViewName, Flag); where: cube, is the name of the cube that has the view you want to export viewname, is the view in the cue that … Continue Reading

This entry was posted in TI Functions. Bookmark the permalink. | Leave a comment

ViewExtractSkipCalcsSet TM1 Function: Syntax and Use

This is one of a set of functions that define the behaviour of a Turbo Integrator AsciiOutput. The ViewExtractSkipCalcsSet function sets the output to either extract rollup calculated (as distinct from rule calculated) values or not, depending if a flag is set (0 for export, 1 for skip). It is the equivalent of the Skip Consolidated Values option in the View Extract dialog box. Why would you use it? The primary … Continue Reading

This entry was posted in TI Functions. Bookmark the permalink. | 1 Comment