Cryptic TM1 Messages Decoded

[iansdigby]

On running any TI process that, inter alia, populates a cube:

TM1speak (in message log) : "Cell type is real"

Human speak: "You specified that a data variable was of type Numeric but the cube cell you are sending it to is a string cell".

(or vice versa?)

[Alan Kirk]

On running any TI process that, inter alia, populates a cube:

TM1speak (in message log) : "Cell type is real"

Human speak: "You specified that a data variable was of type Numeric but the cube cell you are sending it to is a string cell".

(or vice versa?)

Real = Numeric. You'll sometimes come across an error like "cannot convert {whatever} to real" (can't recall the exact syntax of it); it means that whatever is trying to be input to a cell or otherwise manipulated cannot be converted to and/or is not numeric.

Edit: I expected that this would be referred to somewhere in the documentation, but the only place I can find it is in the API manual which is a place that most of those who don't wish to look programming death in the face and laugh at it will avoid. Page 10 of the 10.1 manual:

Code: Select all

Value                  Description
TM1_REAL          A double precision IEEE floating point number.
TM1_STRING       A character string whose length does not exceed 64K bytes.
TM1_INDEX          A 32 bit unsigned integer.
TM1_BOOL          A logical value stored as 1 to indicate TRUE, 0 to indicate false.
TM1_OBJECT       A structure used to refer to objects managed by the API. Typically an object contains information about the server in which the object resides, and an index to locate the object within the server.
TM1_ERROR        A structure containing typically an error code and an error message string.
TM1_ARRAY        An array of values.

Items 1 and 2 are the only ones that apply to values stored in a cube, though.

[Wim Gielis]

Another one:

Data spread failed.

You are a read-only user - as set in the }ClientProperties control cube - and you try to edit a numeric cell.

[GWT]

"failed to create empty document" when double-clicking on a SUBNM in Excel.

Try deleting the .tbd files in %appdata%\Applix\TM1

[gtonkin]

Process "xxx": Invalid parameter array size: Could not initialize process

You also get a failure on opening the error log and the log$ file remains.

The cause of this error is due to a drill process being created against cube A but the drill Assignment belongs to cube B i.e. the cubename in the parameters of your process is not the same as the one being drilled from.

[lotsaram]

Process "xxx": Invalid parameter array size: Could not initialize process

You also get a failure on opening the error log and the log$ file remains.

The cause of this error is due to a drill process being created against cube A but the drill Assignment belongs to cube B i.e. the cubename in the parameters of your process is not the same as the one being drilled from.

Yes it's a right PITA that TM1 doesn't let you have truly generic drill processes. The closest you can come is to replicate a generic drill process per cube with count of N dimensions.

[iansdigby]

A couple of favourites from older versions:

On cancelling a text output operation:
'Stop Now?'

On logging off an instance through the Explorer:
'Disconnect self?'