This has been reported to our development team and will be resolved in an upcoming release as Lisa indicated.
View solution in original post
