List defaults are not set properly if the current selection is specified before the list is populated

[inviscid]

It appears there is currently an order of operation constraint that requires things with lists (e.g. SelectList) to have all of their data populated before the current selection is specified. If the current selection is specified before the data is populated in the list then it is ignored. However, if the current selection is specified after the list is populated it is honored as expected.

This is not desired behavior if there is a way around it. The order of operations should not be a constraint if it can be helped.

[inviscid]

I believe this was fixed in some way to address this issue. It currently operates correctly in the live environment but I'm not sure if this is something custom or this issue was fixed.

Can we update this issue with more info or close.