Hi DVersiga84,
Thank you for the feedback. I reproduced your issue in 4.1.1, but it seems fixed in our internal build. 4.2 should be out very soon, but the fix may or may not be included in that. If not, it will be coming in one of the updates soon after.
Have a good day.
Thanks, TJ