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.
Yes, from what I see, you do not need any additional logic such as data buffers. Maybe something to clear the durable data as rhankey suggested.
You can use the scenario member formulas if you want the seeding to run during every single consolidation of the forecast scenario, or use a custom calculate to trigger the seeding e.g. via a workflow process step if the seeding should only happen on demand. There are more options, but these two approaches are probably the most common ones.
Also, try to use Api instead of BRApi where possible for better performance. E.g. your TimeName string I assume can be set with Api.Pov.Time.Name.
For everything else, more detailed requirements are necessary.
