Custom Command Parameters Bug

Question

Hello,

I believe I've come across a bug in 2019.1. When working inside a custom command with two parameters, I'm trying to add conditions to an Else if statement that look at the two parameters. When trying to add the second condition it simply overwrites the existing parameter condition, and doesn't allow me to have both parameters conditions under the same else if. I've tested this with the top level if statement and it works, but not inside an else if statement.

Any thoughts on how to make this work?
Thanks!

Answer 1

Hello Ryan,

We confirm this is an issue in Adaxes. We will fix it in the next release. For now, you can use the If PowerShell script returns true condition instead of the If one. In the condition, use the below script. In the script, the $valueToCheck variable specifies the value that will be compared with the parameter value. If you need the script to return true when the parameter is checked, use the corresponding value specified in the parameter configuration.

$valueToCheck = "1" # TODO: modify me
$parameterValue = $Context.GetParameterValue("param-AddPhoto")

$Context.ConditionIsMet = $parameterValue -eq $valueToCheck

If this workaround does not meet your needs, we can provide you with a custom build of Adaxes that will include a fix for the issue.

Comments

That's perfect. Thanks!