TM1 Forum

This is version 10.1.1

I just got a very strange error where TI generated a CELLPUTN function that had an extra comma. I fixed it by reselecting the cube on the Maps tab, but I thought it was really weird. Has anyone else run into this sort of thing?

Interesting, I haven't ever really used the wizard so maybe someone more accustomed to it will provide an obvious response but since you are on v10, it's not relating to a cube that previously had a different number of dimensions and then had a dimension added/removed through performance modeler?

Most people don't use the GUI within the processes. I only use the GUI to quickly generate a formula. Then I revert all variables to other. I don't think anybody relies on the GUI for running anything. If your new to TM1 you might not be aware of the GUIs issues. If you are welcome,

Jim.

declanr wrote:Interesting, I haven't ever really used the wizard so maybe someone more accustomed to it will provide an obvious response but since you are on v10, it's not relating to a cube that previously had a different number of dimensions and then had a dimension added/removed through performance modeler?

Nope. It was a brand new process that was filling a cube up from an ODBC connection where none of the variables had to be adjusted and the data was just dumped into the cube as is. I would only use the wizard in this simple instance. I was getting ready to just write out the function myself if it wasn't going to work by reselecting it.

I've seen it happen a few times in my models in 9.5.2, so it's not limited to 10 either. I rarely use the GUI though...


...and i'm still at Editorsaurus

Never seen this one before. That said, I rarely ever use the wizard, so chances are very small I would see that error

This can happen as the TI wizard only rewrites the generated code when you click on the advanced tab, not when you change the settings in the Maps tab. So you can get situations where old code is evaluated against variables which no longer exist, or have changed name etc.

I've notice that if you accidentally map the same variable to 2 different dimensions on the dimensions tab, it will generate code with a blank, hence 2 commas next to each other.

Another strange issue with the Editorsaurus, it happens when connecting to a Cognos package using the connector:
See the different attachments below, right below the "Generated statements" area.
The ONLY thing I do, is saving. Upon each save, 2 lines of whitespace are added