laptop and a wrench

Bug

Long integer or double data types do not persist between Excel and ArcGIS Pro when all values in the column are null.

Last Published: November 26, 2019 ArcGIS Pro
Bug ID Number BUG-000126855
SubmittedNovember 19, 2019
Last ModifiedJune 5, 2024
Applies toArcGIS Pro
Version found2.4.2
Operating SystemN/A
Operating System VersionN/A
StatusKnown Limit

Additional Information

This is a known limitation. The drivers make assumptions about the CSV field data types based on the first row of data. A blank (or null) value is to be translated as text. Create and modify a schema.ini file to 'force' a data type for a field in a CSV file. Additional help documentation can be found here in the following link, https://pro.arcgis.com/en/pro-app/help/data/tables/add-an-ascii-or-text-file-table.htm.

Workaround

  1. In Excel, add a single integer to the column that should be entirely null.
  2. After the integer is added, change the data type to Numeric, and add the appropriate number of decimal places. 
  3. Save the table as a CSV, and add it to ArcGIS Pro. 
  4. The data type for the field is listed as 'Double' or 'Long', depending on the type of numeric data type selected in Excel. 
  5. Perform an operation such as 'Copy Rows', which creates a copy of the data that can be edited. 
  6. Remove the integer from the field in question. 
  7. Check the data type using 'Field View'. Note that the data type retains the proper numeric format, either 'Double' or 'Long', depending on which was chosen. 

Steps to Reproduce

Bug ID: BUG-000126855

Software:

  • ArcGIS Pro

Get notified when the status of a bug changes

Download the Esri Support App

Discover more on this topic

Get help from ArcGIS experts

Contact technical support

Download the Esri Support App

Go to download options