This is fixed in our next "engine" release on Wednesday December 16th. Thank you for reporting the issue.
View solution in original post
