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

MarioGV's avatar
MarioGV
New Contributor III
2 years ago
Solved

when consolidate and translate all CF were deleted

hello, good day; I created a new finance rule calculating the cash flow accounts using as source the balance sheet accounts, the hierarchy is not part of the balance sheet, it's at the same level; wh...
Finance
  • JackLacava's avatar
    JackLacava
    2 years ago

    When running a calculation, any calculated data pointing to the same Cube/Scenario/Period/Entity/Parent/Consolidation intersection (i.e. the DataUnit / Level 1 DataUnit) gets cleared (assuming "Clear Calculated Data During Calc" is set to True on the Scenario, which it will be by default).

    However:

    • if the a previous formula or calculation run marked records as durable (e.g. with api.Data.Calculate("something", True), such data will not be cleared. In order to clear it, you have to explicitly call api.Data.ClearCalculatedData with the parameter "clearDurableCalculatedData" set to True. Durable data is typically created with Custom Calculation routines, so if your Balance accounts are populated through such a routine, this is probably the case.
    • if you're running your new code in a Custom Calculate, the dataunit might not be entirely cleared. Depending on the setup, Custom Calculate might modify just a slice of data.
    • If the data is on base members and it was populated with an Import, it won't be deleted as part of calculation.

    Does this answer your question?

JackLacava's avatar
JackLacava
Icon for OneStream Employee rankOneStream Employee
2 years ago

When running a calculation, any calculated data pointing to the same Cube/Scenario/Period/Entity/Parent/Consolidation intersection (i.e. the DataUnit / Level 1 DataUnit) gets cleared (assuming "Clear Calculated Data During Calc" is set to True on the Scenario, which it will be by default).

However:

  • if the a previous formula or calculation run marked records as durable (e.g. with api.Data.Calculate("something", True), such data will not be cleared. In order to clear it, you have to explicitly call api.Data.ClearCalculatedData with the parameter "clearDurableCalculatedData" set to True. Durable data is typically created with Custom Calculation routines, so if your Balance accounts are populated through such a routine, this is probably the case.
  • if you're running your new code in a Custom Calculate, the dataunit might not be entirely cleared. Depending on the setup, Custom Calculate might modify just a slice of data.
  • If the data is on base members and it was populated with an Import, it won't be deleted as part of calculation.

Does this answer your question?