Page 1 of 1
Cannot convert field number 14, value "@None" to a real numb
Posted: Fri Mar 09, 2012 10:19 am
by Christian Koenig
Hello all,
i try to Import Values from one Cube to another over TI Prozess. The Datasource for the TI Import Process ist a view from the Target Cube
I have no Idea whats wrong and hope someone can help me soon
"@TOT","@TOT","1010","@TOT","@TOT","CAD","@None","@None","REPOBT","BASEET","P10030","AC","1202","@None","1202","0_","200712","Monthly","122604.",Data Source line (1) Error: MetaData procedure line (0): Cannot convert field number 14, value "@None" to a real number.
Re: Cannot convert field number 14, value "@None" to a real
Posted: Fri Mar 09, 2012 10:33 am
by Christopher Kernahan
Hi Christian,
It sounds like Field 14 is a String, not a Numeric value. To use this as a number you need to encapsulate it inside StringToNumber() in the TI process. However, I don't know what you would expect to be able to convert @None into as a real number, so the Metadata process may need some thought.
Re: Cannot convert field number 14, value "@None" to a real
Posted: Fri Mar 09, 2012 4:18 pm
by qml
Christian, check the Variables tab and change the type of any variables that are not guaranteed to always return a numeric value to string. Then in your code you can always apply more convoluted logic, for example check if the variable does not hold "@none" or some other string and if it doesn't just convert it to a number like Chris K has suggested and load to the cube.
Re: Cannot convert field number 14, value "@None" to a real
Posted: Mon Mar 12, 2012 12:32 pm
by ChrisF79
qml wrote:...apply more convoluted logic
This was good for a Monday morning laugh.
Re: Cannot convert field number 14, value "@None" to a real
Posted: Mon Mar 12, 2012 3:03 pm
by Christian Koenig
Found the Solution. It was wrong spelling in the formula. Thanks all for helping me
Chris
Re: Cannot convert field number 14, value "@None" to a real numb
Posted: Mon Aug 16, 2021 5:13 pm
by John Hammond
Thanks everyone got this in Perspectives using a cube view as input with all dims defined as strings.
The cure was to change the view being used as a template in the Datasource section of the TI and accept keep all variables.
Don't know why it fixed it, but it did.