TM1 Forum

Hi All,

I am looking for a alternative to rules for following situation.

I have one consolidation dimension and one measure dimension which includes dates input.

Following is an example

-----------------Value-------Approval Date---------Exp Go Live Date
TOTAL---------5000--------Crap -------------Crap
Item 1---------2000--------01/01/2011-----------03/05/2011
Item 2---------2000--------04/01/2011-----------05/05/2011
Item 3---------1000--------05/06/2011-----------07/07/2011


I dont want date consolidation but By default it does.
Putting rule is a very easy option.. but i am looking for some more efficient way to avoid rule and calculation overhead.(Geek was here..)
Is there any way to achieve this?

Regards,
Lav

There are only two ways I know of to do this:

1) Create a rule to make Approval and Go Live 0 when consolidated, or,

2) Change your date fields to be strings instead of date serial numbers.

lav4you wrote:Putting rule is a very easy option.. but i am looking for some more efficient way to avoid rule and calculation overhead.(Geek was here..)
Is there any way to achieve this?

What rule inefficiency or calculation overhead are you speaking of exactly for this particular circumstance? As it is a C rule no feeding is needed, and unless you have a need to do some traversing of the children to find the first or last date (Min, Max) then there's also so little to be practically no overhead in a rule to simply override the displayed consolidation, say C: 0; or C: UNDEF;

I always store dates as numbers and convert to strings as necessary. If date consolidation becomes an issue, it's ['...'] = C: 0; for me.

Why would you do it any other way? A date string is useless until you convert it to a date serial anyway, which is a fairly expensive operation, as it involves string parsing.

The only exception to this rule was when building Contributor applications in the earliest version of TM1 Contributor. In that case there was a bug that stopped the TM1Web view from parsing the date and converting to the appropriate date serial, as Excel does. I believe this is fixed now.