The OneStream Community is temporarily frozen until June 29th due to the ongoing maintenance. Please read the blog post here to learn more.
Forum Discussion
Solved
Databuffer not working in an WS Assembly rule but is working in a Business Rule
Hi,
I ran into an issue that a data buffer rule does not work in a workspace assembly but does work in the Business Rules area. The data buffer rule is the one found in this forum topic and is relatively simple. See link.
Question: Is there an option to clear non-calculated data in a “bulk” (as known from hs.clear) other than looping through the data buffer and use “SetDataCell” (which has a higher performance impact)? The “ClearCalculatedData“ is not impacting input/imported data – right? | OneStream Community
I have this rule in an existing custom calculate rule in the assembly and the rule fails to get the source data buffer. I take this same rule and include it in a new Business Rule and it runs fine.
Rules that work in the business rules should work in assemblies also.
The destination data buffer needed the View (e.g. V#YTD) to be set. I didn't realize the View was required. My POV pane's View was set to Annotation which I understand is what the data buffer looks to if a dimension is not set in the rule (or Data Management Step POV). The rule works now.
3 Replies
- JackLacava
OneStream Employee
Calculation Rules that work in business rules *do* work in assemblies too - they might just need a bit more context. If you post it, people might find what is missing.
Hi JackLacava
Update: Please ignore. I figured, that the first entity it checks have no data thus blank results. :)
Why does this rule not work in Assemblies but works in BR custom calculation? My job is running, no errors, but there is no data in the log. I have tried filtering and even minimizing to a single account, but still no data. May I know what I am missing here? Thank you.
The destination data buffer needed the View (e.g. V#YTD) to be set. I didn't realize the View was required. My POV pane's View was set to Annotation which I understand is what the data buffer looks to if a dimension is not set in the rule (or Data Management Step POV). The rule works now.
