Numéro d’ID de bogue |
BUG-000174571 |
Envoi | February 26, 2025 |
Dernière modification | March 6, 2025 |
S’applique à | ArcGIS Pro |
Version trouvée | 3.3.2 |
Système d’exploitation | Windows OS |
Version du système d’exploitation | 11.0 64 bit |
Statut | As Designed
Après examen par l’équipe de développement, il a été déterminé que ce comportement est prévu. Pour plus d’informations, reportez-vous à la section Informations supplémentaires.
|
Informations supplémentaires
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.
Solution de contournement
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
Étapes pour reproduire