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?)
Cryptic TM1 Messages Decoded
-
- Community Contributor
- Posts: 109
- Joined: Thu Feb 26, 2009 8:44 am
- OLAP Product: TM1
- Version: 9 + 10 + Plan An
- Excel Version: All
- Location: Isle of Wight, UK
Re: Cryptic TM1 Messages Decoded
"the earth is but one country, and mankind its citizens" - Baha'u'llah
- Alan Kirk
- Site Admin
- Posts: 6002
- Joined: Sun May 11, 2008 2:30 am
- OLAP Product: TM1
- Version: PA2 Classic (PAW-free zone)
- Excel Version: 2010 and 2016
- Location: Sydney, Australia
- Contact:
Re: Cryptic TM1 Messages Decoded
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.iansdigby wrote: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?)
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.
"To them, equipment failure is terrifying. To me, it’s 'Tuesday.' "
-----------
Before posting, please check the documentation, the FAQ, the Search function and FOR THE LOVE OF GLUB the Request Guidelines.
-----------
Before posting, please check the documentation, the FAQ, the Search function and FOR THE LOVE OF GLUB the Request Guidelines.
-
- MVP
- Posts: 2280
- Joined: Mon Dec 29, 2008 6:26 pm
- OLAP Product: TM1
- Version: PAL 2.0.8
- Excel Version: Office 365 - latest
- Location: Brussels, Belgium
- Contact:
Re: Cryptic TM1 Messages Decoded
Another one:
You are a read-only user - as set in the }ClientProperties control cube - and you try to edit a numeric cell.Data spread failed.
Best regards,
Wim Gielis
Excel Most Valuable Professional, 2011-2014
http://www.wimgielis.com ==> 109 TM1 articles and a lot of custom code
Newest blog article: Set up a TM1 model with AutoHotKey as a service or application
Wim Gielis
Excel Most Valuable Professional, 2011-2014
http://www.wimgielis.com ==> 109 TM1 articles and a lot of custom code
Newest blog article: Set up a TM1 model with AutoHotKey as a service or application
Re: Cryptic TM1 Messages Decoded
"failed to create empty document" when double-clicking on a SUBNM in Excel.
Try deleting the .tbd files in %appdata%\Applix\TM1
Try deleting the .tbd files in %appdata%\Applix\TM1
- gtonkin
- MVP
- Posts: 742
- Joined: Thu May 06, 2010 3:03 pm
- OLAP Product: TM1
- Version: PAL 2.0.3
- Excel Version: 2016 64-bit
- Location: JHB, South Africa
- Contact:
Re: Cryptic TM1 Messages Decoded
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.
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.
-
- MVP
- Posts: 3328
- Joined: Fri Mar 13, 2009 11:14 am
- OLAP Product: TableManager1
- Version: PA 2.0.x
- Excel Version: Office 365
- Location: Switzerland
Re: Cryptic TM1 Messages Decoded
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.gtonkin wrote: ↑Fri Nov 29, 2019 8:00 amProcess "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.
Please place all requests for help in a public thread. I will not answer PMs requesting assistance.
-
- Community Contributor
- Posts: 109
- Joined: Thu Feb 26, 2009 8:44 am
- OLAP Product: TM1
- Version: 9 + 10 + Plan An
- Excel Version: All
- Location: Isle of Wight, UK
Re: Cryptic TM1 Messages Decoded
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?'
On cancelling a text output operation:
'Stop Now?'
On logging off an instance through the Explorer:
'Disconnect self?'
"the earth is but one country, and mankind its citizens" - Baha'u'llah