MetaStrategy-Parameter-lock

If you lock a Strategy, including a MetaStrategy, you can still change parameters, but you cannot Save the Strategy.

I just went through it and it seems to working fine as far as I can see. Can you tell us step by step what you are doing and what you think is not working correctly?

Although you don't have to unlock the strategy to change the parameters, you need to unlock it to save a new set of parameters. So, you'll have to, 1) Unlock, 2) modify parameters, 3) Save, and finally 4) Lock.

thank you both. I think I can narrow down the issue with your response.
Taking Starting Capital (80k) as an example of parameter; Unlocking and Saving metastrategy(A) does indeed preserve the parameter value at its next opening.

However when I open a workspace with 3 metastrategies(A,B,C), Starting Capital on each of the strategies is reset to 100k (different to the value saved separately for metastrategy(A) above). Changing Starting Capital on each of the metastrategies to other values and saving the workspace does not keep the values for its next opening, but reset value to 100k again.

I would think the Starting Capital assigned to metastrategy(A, B or C) in a workspace may be different to the ones assigned in metatrategy(A, B) of a different workspace. Hence saving independent (Strategy Settings tab) parameters of metastrategies for each workspace seems important.

Workspace: now this looks like an important missing link.

Based on all above, what is the better way for retaining metastrategy parameters (for ex. Starting Capital) saved for any workspace? Thank you

QUOTE:
However when I open a workspace with 3 metastrategies(A,B,C), Starting Capital on each of the strategies is reset to 100k (different to the value saved separately for metastrategy(A) above).

I can confirm the bug.

The starting capital of each MS component isn't used. Each MS gets a capital allocation based on its Portfolio Weight multiplied by the starting capital in the main Strategy Settings. I do see that starting capital not preserved in the WS though so I'll take a look.