I'm hoping to use Batch Update Fields tool to (amongst other things) display numerous fields of float-type numbers with 0 trailing decimals (as if they were integers), but retain the actual data. The reason for this has to do with wanting to publish to an online hosted feature class and not have to individually change the display for every attribute, but to retain the more precise data for some on-the-fly calculations. I am working on a table in a geodatabase.
When I use the Output Schema Definition Table and set the column specified in the tool's "Output Field Decimals or Length" parameter to 0 (with the Field Type set to Float), the resulting attribute table actually rounds the data to integer values. However, if the Length parameter is set to 2, the resulting values are displayed to the hundredth (#.##), while the original precision is still present in the table. That is, if you double-click on a value in the table, it will display additional decimal places.
This behavior seems to suggest that the tool is handling a Length value of 0 very differently than it is for other values. Any thoughts?
