Hi everyone,
I have an interactive automation script that updates a parameter in a table row using dummy.SetParameterByPrimaryKey()
. The parameter is of a discreet type with four options. However, selecting one specific option triggers a QAction
in the associated protocol, which deletes the row.
When my script attempts to set this parameter to the triggering option, it eventually fails because it tries to verify that the parameter was successfully set—but the row no longer exists due to the QAction
.
Is there a way to bypass this verification in my script without resorting to a try-catch block?
Thanks in advance!
You could disable the get after set verification by updating the runtime flag ‘NoCheckingSets’
e.g. engine.SetFlag(RunTimeFlags.NoCheckingSets);