Hi, The fix for the issue will be available in next LIB version (2018.2.528). It will also be included in our next official version – R2 2018 SP1, scheduled for the end of June. Best regards, Ralitsa Kumanova
hi, any upates on this? I need this bug solved, are there workarounds in the meantime?