Bug ID Number |
BUG-000174571 |
Submitted | February 26, 2025 |
Last Modified | March 6, 2025 |
Applies to | ArcGIS Pro |
Version found | 3.3.2 |
Operating System | Windows OS |
Operating System Version | 11.0 64 bit |
Status | As Designed
After review by the development team, it has been determined that this behavior is as designed. See the Additional Information section for details.
|
Additional Information
Adding the same CSV to an ArcGIS Pro map and opening the attribute table causes the CSV reader to interpret the 012 value as a number, removing the leading zero instead of preserving it as text. The Export Table tool uses the same ArcGIS Pro CSV reader, ensuring consistent behavior across the application. Input field types and values match those displayed in the attribute table. The field map parameter modifies the output field type but does not alter input field properties or their interpretation. Clicking Edit on the field map and viewing the Source Fields section reveals that the input source field is a numeric type, with the leading 0 already removed.
This is not considered a defect. To propose an alternative method for modifying CSV field properties beyond schema.ini, submit an enhancement request on the ArcGIS Pro Ideas site for further discussion and requirement gathering. The Export Table tool must maintain the same approach as the attribute table for reading values, ensuring consistency by using a shared CSV or Text file parser.
Workaround
Follow this workaround to create a schema.ini file to define the data types of the CSV file before using the tool. https://support.esri.com/en-us/knowledge-base/how-to-edit-the-field-properties-of-a-csv-file-in-arcgi-000024378
Steps to Reproduce