Hi @seehowtwo
potentially, yes, the issue is caused by un-escaped quote marks.
I have not experienced this issue before, so it could be server specific.
Easiest way to get the field back working is remove the quote marks and update the corresponding string count
