Hello,
We are currently experiencing a data export problem where some data is missing.
Calculation rules are applied to this data and on the day before export we don't export this data because it is equal to 0, but on the day of export this data does have a value and is therefore exported.
This rule is based on real dates: if the current date is less than or equal to a date entered in a parameter in a cube, then the data is equal to 0. If the current date is strictly greater than the parameter date, then the data is equal to a value (a value equal to a similar cube intersection but with only one dimension changing).
We therefore have a calculation rule based on the current date (Today() function) and a date specified in a parameter.
We'd like to know what good practice is for rules like these.
Best regards,
Alexandre

Have you checked that you do not have rule-based values skipped in the source of the TI? ViewExtractSkipRuleValuesSet (CubeName, ViewName, 1); if this is set to 1 it will skip rule based values.  

Hello Terry Hamlet,

I've just checked and we do have a ViewExtractSkipRuleValuesSet (CubeName, ViewName, 0) in the process so it's not that but thanks for the help and information. 

Best regards,

Alexandre

Hi Alexandre,

Have you checked to make sure your rule calculations are properly fed?  If the outcome shows, but is not fed, the TI process will not pick it up.  If you are using PAW (Data and Models), unfortunately my experience you cannot trust the tool to tell you if the data is fed.  I have seen multiple times where PAW says fed and architect (rich tier) shows it actually is not.  I suggest testing with zero suppress and/or architect to see if the cell(s) is fed.

Best Regards,

Terry

I am not sure the issue is clear to me. Is the value calculated in the cell but not exported? If so I believe what Terry noted is the resolution. 

As for using TODAY() in rules, I would recommend using a CELLGET to a variable-type cube with a value equal to the current day. This could be updated daily as part of a Chore/TI but could also allow an admin to adjust/change the value without updating rules. 

Hello Ryan Sinclair,

Thank you, but I don't quite understand how this will prevent problems. 

Best regards,

Alexandre

Hi, 

You requested 'We'd like to know what good practice is for rules like these." In my perspective, that would be a better practice than using a TODAY() function within a rule. 

As for the actual issue, I'd second Terry's question/comment. If the source view is constructed correctly to capture that cell and data, it would appear that the rule is not fed correctly.

Thanks,

Ryan