I was able to reproduce this issue not only in the List module but in other content modules as well. Unfortunately this looks like a bug on our side. I have logged a bug in our internal bug tracking system and have created a PITS issue - here is the public URL -
I have updated your telerik points for the discovery.
Yes, this might fix the issue temporary but if you somehow upgrade your project or cause a model redefinition, OpenAccess will recreate the database field with its old definition.Greetings,
I am sorry to hear about your frustration. I will make sure the fix for this bug gets pushed to production as soon as possible. Again, apologies for the inconvenience.Greetings,