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

DC's avatar
DC
Icon for OneStream Employee rankOneStream Employee
4 years ago

Scenario Setting - Retain Next Period Data Using Default View - Next Period Reversing

We have data imported periodically to a Scenario with the following setup - Retain next to True and everything set to Periodic inclusive of the data source and TR as shown below.  The account is an E...
Data Integration
db_pdx's avatar
db_pdx
Valued Contributor
4 years ago

Hi DCruz: ooo, this sounds familiar.  We have a few scenarios that run Periodic input (with exactly the same settings as your 1st screenshot) and we had some problems as well.  From memory, a few things to check:

  • Is the scenario fully consolidated?  Try a force consolidate on M12
  • Have you changed any of the scenario settings after you did the load?  I believe this caused us some issues like you are experiencing.  If so, fully clear the data unit, reload, and reconsolidate
  • Have you changed the account type after you did the load?  As above, we've run into weird edge cases where this doesn't consolidate properly the next time depending on what account types you are switching between.  If so, clear the data unit, reload, and reconsolidate.
  • Are you doing any parallel loads that might result in the same data intersections being hit?  We believe, but have been unable to consistently replicate, a bug with parallel loads.  Switching back to sequential has resolved the issue, albeit with slower load times.

We had best results when fully clearing dataunits from Data Mgmt jobs.  If you cannot do a full clear you can try a targetted BR clear via CustomCalculate and see if that does the trick as well.

Hope this helps.

Cheers,

DB