The fix for this issue will be available in the next LIB version (2018.2.806). It will also be included in our official version – R3 2018, scheduled for the mid of September.
Hi Tim, Please excuse us for the delayed reply. I am afraid that by the time being, there is no progress on the issue. It is, however on top of our backlog and will be available in one of the next libs. Please click "Follow this item" in order to be subscribed to latest notifications regarding the issue. All the best, Stefan
Is there any update on this matter?