TM1 Forum

Hi,

We recently upgraded from TM1 v9.5.2 to v10.1.1 along with a lot of TM1 Web excel files. DIMIX and DIMNM are used extensively to get the dimensional element from the Alias element name and it worked perfectly fine in v9.5.2

However DIMIX is not working in v10.1.1 when used as said in below documentation DIMIX(dimension, alias element name) - am i missing something or is this a bug?
eg. DIMIX("Location", "United States of America") -> should return 5 (like in v9.5.2) however returning 0 always
Location - Dimension
United States of America - Dimension alias name for USA element

http://publib.boulder.ibm.com/infocente ... _wrk_dimix

Thanks & Regards,
Logan

Dimix still works for me in 10.1.1.

How are you getting to your alias? Is it just a subsetelement in an active form? Is it typed in somewhere? Is it the result of a DBRW?

Are you seeing this in both excel (through perspectives) and when the sheet is uploaded to the web... or just one or the other?

LoganNSE wrote:DIMIX("Location", "United States of America")

Just relooked at your comment your problem could be that it should be:

Dimix ( "ServerName:Location","United States of America")

Rodger,

TM1RPTROW with MDX is used to get a list of alias element names in specific order and used DIMNM(.., DIMIX(..)) to get the actual dimension element name.

It doesn't work in both Excel perspectives and TM1Web - just returned empty. I tried hard-coding DIMIX with alias element name in excel perspectives, it returned 0 and when used with element name, I got the correct index.

Yes, I used DIMIX("ServerName:Location","United States of America") with ServerName.

Thanks.

Just rule out problems in the other "direction", did you check that your aliases were preserved through the upgrade?

Steve,

Yes, Alias is present and I manually checked.

I remodeled the web sheet with modified MDX to retrieve the child items sorted in order to workaround this and it is working fine without using Alias's in TM1RPTROW.

It's worth checking your message log file to see if there are any errors on start-up. A clash (i.e. duplicate values) between alias values on different elements in different dimensions should cause a log error on start-up but the server will appear to have loaded without a problem. Where you have large dimensions automated from an upstream system this can happen. Without checking the log you might not find out... until you start getting weird problems with aliases in both active forms and standard slices. I'd rate this as having a higher chance than fix-pack weirdness as being root cause for your issue.