TM1 Forum

Hi,

I checked the forum, but honestly I have not even idea on what/how to search this, so apologize if something similar has been posted already.

I have an implementation TM1 10.1 and I have this problem:

I have a button that is creating an element based on 2 subnms and a name
i.e.

I select elem1 from a combobox on subnm1
I select elem2 from a combobox on subnm2
I have a "free"name box

I want to achieve something like

xxx_elem1_xxx_elem2_yyy

it works quite well except for the fact that on a very limited amount of cases it seems that the string generated is something like:

xxx_='Sheet1'!$G$36_xxx_elem2_yyy
where obviously Sheet1 G36 is the position of the subnm.

the weird thing is that it happens only once in a while on random users without any apparent reason.

There are users with a number of correct strings near 20, 30 and maybe 0 errors, or 1 at maximum.

Any idea what it can be?


EDIT:
I got an user live on video conference and it seems that when this error occurs, the system opens without layout, meaning ïnvisible buttons, no colors, no layout whatsoever.

Not that it directly helps with why your websheet is being flakey but one option you have is to test for the presence of elem1 and elem2 in their appropriate dimensions before you go ahead and add the new element. E.g. Although this doesn't solve the source problem, it at least prevents the unwanted element getting created. Did you know it is possible to configure the action button to give a customized error message? So, you can let the user know that a problem occurred.

rmackenzie wrote:Not that it directly helps with why your websheet is being flakey but one option you have is to test for the presence of elem1 and elem2 in their appropriate dimensions before you go ahead and add the new element. E.g.

Code: Select all

nCheck1 = DIMIX ( 'dim1', elem1 );
nCheck2 = DIMIX ( 'dim2', elem2 );
IF ( nCheck1 <> 0 & nCheck2 <> 0 );
  # safe to insert the new element...
  #DimensionElementInsert ( etc etc
ELSE;
  # some sort of problem has occurred
  # potentially the one you've observed
  # so perform some sort of error handling
ENDIF;

Although this doesn't solve the source problem, it at least prevents the unwanted element getting created. Did you know it is possible to configure the action button to give a customized error message? So, you can let the user know that a problem occurred.

actually the elements are not empty,

they are taken as string and the string is the formula.

I checked also if it was a problem of excel cell type but it doesn't seem so.

stingo wrote:actually the elements are not empty,

they are taken as string and the string is the formula.

DIMIX will return 0 if elem1 is blank, or if it is some string that doesn't match to an element in the dimension.

In your example ='Sheet1'!$G$36 is unlikely to be an element in dim1 so the insert into dim3 won't happen.

Note I mentioned I wasn't proposing a solution, but a work-around.