@alien4u @nzy @michoel we had a case started with support and they have closed the defect as it has been resolved with 2018.1. Got the update this morning.