@TurboTaxAniqua , since you are aware of the issue, can we get an ETA on this bug fix for next release ?
