TM1 Forum

Can we substitute attribute instead of DIMIX .How could it enhance performance of the TM1.Thanks

TM1ethusiast wrote:Can we substitute attribute instead of DIMIX .How could it enhance performance of the TM1.Thanks

Leaving aside the fact that attributes and DimIx server two completely different purposes:
Request for assistance guidelines (PLEASE READ)

RFA Guidelines wrote:3) Try to make the question as specific as possible. A general question like "How do I write a rule?" is difficult to answer without copying out the whole of the user manual. A question like "I have a payroll cube which contains the following dimensions {details} and a general ledger cube which contains the following dimensions {details}, and although I've read through the Rules Guide I'm still not sure how to write a rule to give me average sales per employee" is far more likely to get the answer your need.

RFA Guidelines wrote:6) Give a brief outline of what you've done to find the answer; which manuals or guides you've looked in, what tests you've done.

I assume you're talking about things like feeding last year to next year? E.g ['Some Value'] => DB('SomeCube', !Dim1, !Dim2, dimnm('Year', dimix('Year', !Year)+1, !Dim4);

You can change this to ['Some Value'] => DB('SomeCube', !Dim1, !Dim2, attrs('Year', !Year, 'Next'), !Dim4);

Obviously you'll need to have an attribute in your "Year" dimension called "Next" that contains the appropriate information. You'll also need a "Previous" attribute for the other half of the rule/feeder combo.

The attributes method is significantly faster than dimix. It's also more reliable because it won't get stuffed up if someone introduces a new element or messes with the dimension order.

Given that your question was rather vague I may have missed the mark completely. If so, please provide more detail.