When a published (user) parameter is defined with a default value but the parameter is set to “Disabled” in the GUI, the default value gets overwritten with the value <Unused>.
I would like this behaviour to be changed so that the default value is not overwritten.
My use case is that I’m trying to build a workaround for the other (as yet unresolved and long time issue) of not being able to persist a default value. (See below)
I’m trying to give the user an option to choose a default value but not have the ability to edit it, hence having it disabled. I’m attempting to implement this by having a choice which lets the user select “Default” or “Custom” value and then enabling/disabling the appropriate inputs.
Here’s what my interface looks like with Query Type set to “Default”:
And here’s what the parameter values look like after obtaining them using a ParameterFetcher:
Even though the default value is set like this:
If I choose “Custom SQL” as my Query Type option then everything works as expected and the value comes through -- even the default value comes through correctly because the parameter is now hidden instead of disabled.
Interestingly, when initially developing the workspace and the published parameters it looks like everything works fine. It’s only when you save the workspace, close it and re-open it that the <unused> value starts appearing.