So, are you recommending that I use a standard calculate function without all the additional logic? I had disabled the 'Clear Calculated Data during calc' option, but it didn’t help much, as the data was not being cleared when running the formula.
You script is a little confusing to me.
What is the purpose of your first Calculate() statement that appears to be zeroing out the data in the target scenario? Those zeros, and even worse when they were written as durable data, are going to get in the way of writing any subsequent values to those cells. Other than in a few isolated instances where the odd zero is required to overcome derived data problem, writing zeros to the cube is bad.
Then why do you subsequently clear what appears to be the same zeroed out data?
As Henning alludes, the Scenario ClearCalculatedDataDuringCalc should normally be True (I similarly have never seen any builds where this has been set False).
Then I'd have a two line BR:
ClearCalculatedData() for all Calculated, Translated, Consolidate and Durable data in current Data Unit
Calculate() to copy desired source data to current Data Unit. I usually write the data as durable, but you need to make sure you're filtering out any data that may need to be recalculated in this Scenario. For filtering, you need to add an If test to check what Data Unit is being processed, and/or using Filters on the Calculate statement.
Run the above two lines for the destination Scenario/Time/Cons/Entities.
There is nothing I see in your current buffer handler that requires the buffer handler.
