Fix for this issue has been released in 2020 R3 version of our component.
↧
Fix for this issue has been released in 2020 R3 version of our component.