Forum Discussion
Henning
3 months agoValued Contributor II
Hi,
first of all, why does it need to be a stored account? Using this for validations pushes data into the database, usually unnecessarily.
Confirmation rules is where validations take place in OneStream, via the workflow. If one wishes to see some validations in a cube view, I tend to recommend dynamic accounts / members. You can also use the annotation member for those, displaying a "fail" or "pass" text instead of a "1".
If you want to go down the route of storing the result, refer e.g. to case 4 of the example given in the documentation:
api.Data.Calculate(“A#MyAccount:F#None:O#Import:I#None:U1#None:U2#None:U3#None:U4#None:U5#None:U6#None:U7#None:U8#None = 1”)
Make sure to specify each dimension in the target (left hand side of the equal sign) and do not use "All" in order to avoid unwanted data explosion.
Related Content
- 2 years ago
- 3 years ago
- 6 months ago