TM1 Forum

Hi,

I had earlier created some drills between cubes in version 9.5. I had tested them and the title dimensions of the target views will be set to the matching elements base on the intersection of the source cell that drill from.

However, I tested the drills again in 9.5.1 and it seems that the title dimensions in the target views remain unchanged! I.e. if I save the target view "Drill_Comment" with "Sep-10" as the title element in the title dimension "Month", and if the month element that I drill FROM is "Jun-10", the resulting view still remains at "Sep-10" together with the originally-saved subset!

For drill, even the saved subset in the title dimension will be replaced by a single-element unnamed subset, but this is not the case now. I have restarted the server as well as my local and the error still occurs.

I tested yet again with 9.4.1. and it is working.

Anyone notices this happening in 9.5.1? This is really critical.

Found this in IBM:

PM17301: DRILL THROUGH ISSUE DURING NAVIGATION CUBE TO CUBE
APAR status * OPEN

Error description *
The new 9.5.1 update introduce a bug in the use of drill
through. Indeed, during navigation cube to cube, context
parameters are no longer kept.


Sigh... why does this always happen? They fix something, and then they break something else... now I have to rollback to 9.5! URRGHH!!!!!

Any update on this?
Is it fixed in 9.5.2?

I hope so...

A quick and dirty workaround for those hit by this.

Put a subset in your view for each of the dimensions you want to be dynamic.
Rename each parameter for each of these dimensions sE1, sE2 and so on.

Put this code in your prolog.

sSubName = 'Your subname here';
#Make sure you keep the order the same as the parameters

sD1='DimName 1';
sD2='DimName 2';
sD3='DimName 3';

ixLoop=1;
mxLoop=3;

While (ixLoop<=mxLoop);
sDimName=Expand ('%sD' | Str( ixLoop ,1,0) | '%' );
sElName =Expand ('%sE' | Str( ixLoop ,1,0) | '%' );
SubsetDeleteAllElements(sDimName, sSubName);
SubsetElementInsert(sDimName, sSubName, sElName, 1);
ixLoop=ixLoop+1;
End;

Yes it's fixed but you do wonder how this made it through in 9.5.1