04-05-2024
07:14 AM
- last edited on
04-05-2024
09:17 AM
by
JackLacava
Rules TIP - ONLY write / use Rules when necessary.
OneStream projects should not be a contest to see who is better at writing complex rules.
If you must write rules please remember:
Conditional statements can be added to formulas to limit which Consolidation calculation processes will do something for this formula.
For Local currency only: If Api.Cons.IsLocalCurrencyforEntity Then
For Translated currency only: If api.Cons.IsForeignCurrencyForEntity Then
For Parent-Child Relationship levels: Api.Cons.IsRelationshipLevel returns True for Consolidation level being OwnerPreAdj, Share, Elimination or OwnerPostAdj.
For best performance, use Remove Functions – Zero and No Data
TIP 2 - Don’t Stack api.Data.Calculate Functions.
Let's say we need to calculate data for the dimension members below. What shall we do?
Instead of the above - do the list below.
For more information:
OneStream Finance Rules and Calculations Handbook.
Level 2: Financial Model Rules course.
Solved! Go to Solution.
04-05-2024 10:07 AM
thank you sir, most important thing to remember
04-05-2024 01:07 PM
@cbriscoe - Thanks.
My 2 Cents
- You can also use Finance Business Rule vs Creating more member formula because it might impact the consolidation time.
- Avoid using api.data.calulate inside the for loop, instead use the DBCL.
04-05-2024 10:07 AM
thank you sir, most important thing to remember
04-05-2024 01:07 PM
@cbriscoe - Thanks.
My 2 Cents
- You can also use Finance Business Rule vs Creating more member formula because it might impact the consolidation time.
- Avoid using api.data.calulate inside the for loop, instead use the DBCL.
04-15-2024 09:42 AM
I like it. True too.
06-21-2024 04:27 PM
I was an instructor of the L2 Finance Business Rules course for 4 years. This is the best 'crib notes' version I've seen to date! Thanks for sharing!