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
why did 1Stream design their workflow to start from / associated with a cube?
Acceptance Criteria: Definition of fixed, expected behaviour
I created this enhancement request with 1Stream - do you agree with me ? Do you have any suggestions to improve 1Stream...
TonyToniTone and LeeBrown,
I'm sure you are more knowledgeable about 1S than I. So while I have your attention, Can I ask a simple question?
How do you handle a sale of a division in your company to other corporations?
How do you handle a sale of a division in your company to other corporations?
For example:
We have a Division1 selling widgets. It is under a consolidation roll-up for external reporting purposes. After we sold it, we want to stop tracking its history of transactions, so we create another member in Entity dimension called Division1_sold, put it under a different 2nd roll-up in Entity dimension. We need it to track and wrap up any costs/ revenue pertaining to Division1 that is no longer ours, and so we don't want to report nor consolidate it under the first roll-up.
Is there a more elegant way to solve this problem? I see that OneStream allows us to set up for each member (such as Division1) that has a date when 100% consolidation begins and ends .
Please do not answer my question here is this thread. I'll create another thread to give you more credit and mark your replies as the "Solution".