Hi, just found that having a chooser with an Evaluate Chooser row, which can reference a second chooser, does not write the value I expect to the output column.
My expectation would be for the nested-most chooser to write the output column, but it’s the main chooser that writes it.
Is this by design?
This is by design, but may be revised.
The reason for the current order is that if a nested chooser fails (eg no rows pass, and it has no fallback), then the outer chooser does not set it’s output values… instead it goes to the next passing row in the outer chooser and tries evaluating that.
One feature which will be helpful for your use case (currently in progress) is the ability to disable cells of output columns. This would allow you to mark the outputs of rows in your outer chooser (where you know there is an inner chooser also outputting that value) as disabled.
We may, however, revisit the order of operations on outputs as well, to better support multi output mode (currently you can’t output an array of structs, along with your array of objects)