Thank you for your post! Regretfully, this was one of those bugs we caught post data fix but pre-release, so we had no choice but to postpone a fix. But it will definitely be fixed, and hopefully before 4.1! Cheers!