| Numéro d’ID de bogue |
BUG-000123119 |
| Envoi | June 18, 2019 |
| Dernière modification | June 5, 2024 |
| S’applique à | ArcGIS Pro |
| Version trouvée | 2.3.3 |
| Système d’exploitation | Windows OS |
| Version du système d’exploitation | 10.0 64 Bit |
| Statut | Will Not Be Addressed
L’équipe de développement a examiné le problème ou la demande et a décidé qu’ils ne seraient pas traités. Pour d’autres explications, reportez-vous à la section Informations supplémentaires correspondant au problème.
|
Informations supplémentaires
This behavior is as intended/as designed. CopyFeatures is intended as a lightweight feature by feature transfer without any additional higher order objects from the geodatabase (subtypes, domains, etc). By being more narrow and lighter weight, it is a bit faster. If the desire is to have all the associated geodatabase objects be copied across, that is the purpose of the FeatureClassToFeatureClass tool, as well as the Copy tool.
Solution de contournement
Use the copy command from the context menu options to directly copy over the feature class to the new file geodatabase within the Catalog pane. https://pro.arcgis.com/en/pro-app/help/data/geodatabases/overview/copy-feature-datasets-classes-and-tables-to-another-geodatabase.htm#GUID-83B928E7-BA8C-4E10-BF74-2D4A97C452C9This issue is not reproducible with the FeatureClassToFeatureClass_conversion() tool. Use the 'FeatureClassToFeatureClass_conversion()' to copy the feature class with domains to the new file geodatabase. The issue is not reproducible in ArcMap 10.7. Running the CopyFeatures_management() tool to create a copy from the same data exports the domains as well.
Étapes pour reproduire
ID de bogue: BUG-000123119
Logiciel: