Output record rejected if JSON text field size exceeds feature class text size.

Discussion created by geasand on Jan 27, 2014
Latest reply on Jan 29, 2014 by rsunderman-esristaff
FYI - I've discovered that if the content of an incoming JSON text field exceeds the text field size of the destination feature class attribute field, the entire JSON record is rejected.  There appears to be no warning of this occurring within GEP.  The GEP monitor will indicate that all records from the input have also passed thru the GE Service and the GEP output.  However, the records will not get added or updated in the target feature class.  It also happens with integer numbers.  If the input integer value is larger than the 32bit range allowed in the Geodatabase then the record is rejected.  It would be handy if a GEP output could detect this situation and produce an error log file listing rejected records with an explanation.