i've run into similar issues with 2.0 scripts... there have been a few occasions i actually had to set an integer field as a string to prevent the error