Attribute Trouble with rules

[kelso]

Hello,

I made a rule that creates an attribute Month and Year that also changes the alias for exchange rate factors. This Month and Year combination goes and finds different exchange rates for my cubes, so the user only has to select what fx scenario he wants.

Example:

---This Month---
Scenario 1 = Sep 2010 = using NOW
Scenario 2 = Aug 2010 = using index and some rules that are updated on a cube and attributes cube
...
Scenario n

---Next Month---
Scenario 1 = Oct 2010 = using Now on October
Scenario 2 = Sep 2010
---
Scenario n

I was testing it and works wonderful doing complex lookups in seconds, but when I tested changing the month on the computer (windows clock) where the tm1 server is mounted, only the alias is changed, leaving the exchange calculus the same. (even the rules tracer marks the correct month and exchenge rate on the rate cube) When I Unload and make a new view the cube works fine.

I believe that TM1 is not detecting this "month changes with attributes" so recalc do nothing. Is like if it needed something like a "Security Refresh" to make changes happen. The only solution I thought was to unload the cubes each night with a TI process. so with a recalc the cube is forced to recognize the new month, of course in case a user is connected at 12:00 am October 1st.

Any Ideas? English is not my first language, if something is unclear please tell me, so I can explain it.

Thanks

[mattgoff]

I believe NOW is only evaluated when you load or save the rule. Unfortunately, I don't think you can do what you're trying to do with rules alone. One workaround would be to schedule a chore to run a process with RuleLoadFromFile.

Matt

[Wim Gielis]

Or:

you could have a chore (or a scheduled TI process) to run every night just after midnight / every month which sets the date in a mini cube or lookup cube.

Then, refer to that cube for current month or similar information / parameters.

[Gregor Koch]

Hi
Rule calculated cells are always calculated on request. This also applies to functions like NOW() or TODAY() etc. the latter might actually be easier for you to use.

I would be very careful when calculating the value of an Alias, though, because it needs to be unique at all times.

Is it possible that you are feeding based on this Alias?

Could you post an example of the rule (or involved rules) and feeders?

Cheers

[kelso]

The process that mattgoff told me about ruleloadfromfile works. I run the process and data is working well. I guess i need to schedule it.

For Gregor,

The feeder applies to all the scenarios, [local]=>[usd] going a !scenario for each usd scenario. I tested many times this. What I figure about your question is that when alias changes, the feeder do not correspond to the "fed" places unless i save again the rules. Because this change occurs only once a month with the ruleloadfromfile process the feeders are automatically refreshed. (If I am wrong please correct me)

Because the rule is automatic same alias shall not appear. I need to leave some scenarios that users can change, so they will need to save the rules again. I thought it was simplier.. but i guess is a nice solution.