Error
| Número de ID del error | BUG-000161939 |
|---|---|
| Enviado | October 6, 2023 |
| Última modificación | June 5, 2024 |
| Relacionado con | ArcGIS Pro |
| Versión encontrada | 3.1 |
| Sistema operativo | Windows OS |
| Versión de sistema operativo | 10.0 |
| Estado | Duplicate |
The best practice for using the arcpy.FieldMapping() and arcpy.FieldMappings() objects is to construct the field mapping by adding the target and input dataset fields using addTable first. The following code snippet produced the expected output for the provided script:
... try: ## Truncate the staging table ap.TruncateTable_management(tblCntyDataStaging) ## Run the arcpy fieldmapper to map field name changes between the two schemas fms = arcpy.FieldMappings() ### Use addTable for target and input per best practices fms.addTable(tblCntyDataStaging) fms.addTable(tblCntyDataSource) ### for field in fieldList_cds: if field.name != "OBJECTID": fm = arcpy.FieldMap() fm.addInputField(tblCntyDataSource, field.name) f_out = fm.outputField f_out.name = fieldMapDict_cd[field.name] f_out.type = field.type fm.outputField = f_out fms.addFieldMap(fm) # Populate the fresh table into the staging table arcpy.Append_management( tblCntyDataSource, tblCntyDataStaging, "NO_TEST", field_mapping=fms ) ...
ID del error: BUG-000161939
Software:
Obtener ayuda de expertos en ArcGIS
Descargar la aplicación de soporte de Esri