Do you know what the other two posts you saw were?
Well done sir! Problem found indeed. I have been able to reproduce this issue in 10.0.5 and will notify you when this release goes live. Your workaround sounds like a pain indeed but I am happy to at least hear there is one. Thank you.
