July 4, 2019 at 6:13 am
Gaurav Sharma
Subscriber

Francois 

The bug has been fixed and the fix would be available in 2019 R3. Thanks again for sharing your observation.

Regards,

Gaurav