Issue introduced by #776, confirmed not to exist in v4.0.0
Test form: trigger.xlsx
I can't immediately explain how this is possible with all the tests passing!
The new behavior is similar to what would previously happen if something invalid were put in the trigger column. Ideally something invalid in the trigger column would throw an error.
Issue introduced by #776, confirmed not to exist in v4.0.0
Test form: trigger.xlsx
setvalueaction is producedsetvalueaction is produced and the calculation is not passed through anywhereI can't immediately explain how this is possible with all the tests passing!
The new behavior is similar to what would previously happen if something invalid were put in the
triggercolumn. Ideally something invalid in thetriggercolumn would throw an error.