Thank you Bruce and Joe for identifying and verifying this issue. I, too, have confirmed the bug. Please contact our sales for the custom build that fixes this issue. It will also be available in the next release tentatively scheduled for this Thursday, 25 June.