Hi Christopher,
We are able to reproduce the problem at our end. We have fixed the issue internally and it will be included in the Volume 1 Service Pack 2, 2017 which has been scheduled to roll out by the end of March, 2017.
Regards,
Seeni Sakthi Kumar S.