Default values can be a bit funny, because of quirks with how they're (not) populated when the list of choices is not known at the very beginning.
One workaround is to have an extender running at dashboard load, pushing a default value directly in the parameter.
Hi Jack,
Thanks for this comment - I'm having this exact problem! Do you happen to have (or has anyone else listening) any example code for a dashboard extender that would push a value into a parameter?
I've been using the following which is essentially using the brapi.dashboards.SetLiteralParameterValue command but I've found it doesn't always work. In fact I believe I might have misunderstood the basic function of this code as what it seems to do is populate the "Default value" of a parameter rather than the actual value assigned to it (the latter is what I'm trying to do).
Any suggestions would be welcomed!
Regards,
Richard
