TM1 Forum

BrianL wrote:In this case multiple commit mode is a red herring. Multiple commit mode ONLY applies to chores. It inserts a commit between each TI that is explicitly defined as belonging to the chore. It has no impact/relevance to processes called by ExecuteProcess. They still run in the parent TI context.

Also, multiple commit mode still defaults to off. Even if the default had changed, TM1 should not be editing your existing chores (to change value) during an upgrade.

Further, all multiple commit mode does is make your changes public to ALL users at each commit point instead of keeping the changes local to the chore/TI that's running until the entire thing finishes running. It should not effect the execution semantics at all.

Seems like you've already narrowed this down to the attributes cube not being empty. What's your code that's supposed to do that?

### SET THE DATASOURCE ###
sFilePath = CELLGETS ( '_Replication' , '_Replication' , 'Rep Filepath' );
sFile = sFilepath | 'DIM_' | DimName | '.cma' ;

DatasourceNameForServer = sFile;
DatasourceNameForClient = sFile;

Cube = '}ElementAttributes_' | DimName;
DimensionDeleteAllElements ( DimName );

### ONLY RUN IF ATTRIBUTES ALREADY EXIST ###
IF ( CubeExists ( Cube ) = 1);
    CubeSetLogChanges(Cube, 0);

### CLEAR ALL ATTRIBUTES TO AVOID ALIAS CONFUSION WHEN REBUILDING STRUCTURE ###
  CUBECLEARDATA ( Cube );

ENDIF;

ElementExists = DIMIX ( DimName , Element );
TopLevel = ELPARN ( DimName , Element );

IF ( type @= 'C' & TopLevel = 0 );
    DimensionElementInsert ( DimName , '' , Element , 'C' );
    Parent = Element;
ELSEIF ( type @= 'N' & TopLevel = 0 );
    DimensionElementInsert ( DimName , '' , Element , 'N' );
ELSEIF ( type @= 'S' & TopLevel = 0 );
    DimensionElementInsert ( DimName , '' , Element , 'S' );
ELSEIF ( type @= 'C' & ElementExists >0 );
    Parent = Element;
ELSEIF ( type @= '' );
    DimensionElementComponentAdd ( DimName , Parent , Element , Weight );
ENDIF;

DimensionSortOrder ( DimName , 'ByName' , 'Ascending' , 'ByHierarchy'  , 'Ascending' );

### ONLY RUN IF ATTRIBUTES ALREADY EXIST ###
IF ( CubeExists ( Cube ) = 1);
    CubeSetLogChanges(Cube, 1);
ENDIF;

lotsaram wrote:Actually ironically I ran into a bug to do with DimensionDeleteAllElements on Friday with 10.2.1

The situation was if DimensionDeleteAllElements is called and then subsequently there are no further metadata actions in the process then the DimensionDeleteAllElements has no effect. (Say for example the data source is empty so non code from the metadata or data tabs is executed). I would have expected the dimension to be empty in such a scenario.

Can anyone else confirm whether this is "expected behaviour" and therefore according to IBM a "feature" vis a vis a "bug"? IMO if the function doesn't do what it says on the can then it's a bug but I hardly ever use DimensionDeleteAll elements and normally prefer to use an unwind approach, but this was for a temp kind of dimension so delete all elements was appropriate.