Ok, thanks!
Hi Rutger, The fix is available since LIB 2016.2.516 and will be part of the upcoming R2 2016 SP1 release. Regards, Yordanka
I've received an email that this ticket was completed, does this mean that this issue is fixed as well? And in which version? As we've submitted this ticket in the past...