| Numéro d’ID de bogue |
BUG-000164103 |
| Envoi | January 3, 2024 |
| Dernière modification | June 19, 2024 |
| S’applique à | ArcGIS Pro |
| Version trouvée | 3.2 |
| Système d’exploitation | Windows OS |
| Version du système d’exploitation | N/A |
| 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
A non-geodatabase database table is used in ArcGIS Pro as a query layer. If that table does not have an ObjectID field (the code sample for creating the table in the database did not specify an ObjectID), the system automatically adds one for use in ArcGIS Pro. This ObjectID field is 64-bit by default. Tables with a 64-bit ObjectID field cannot be exported to legacy formats like dBASE database files, which do not support 64-bit Object IDs or Big Integer fields.
The workaround provided using the option to ensure compatible field types are used allows the table to be added into ArcGIS Pro using a 32-bit ObjectID field, so this table view can then be used as input to export to an output dBASE table.
Solution de contournement
In the Options dialog on the Maps and Scenes page, check the box to Use field types that are compatible with ArcGIS Pro 3.1 and earlier releases when adding query layers and text files.
Étapes pour reproduire
ID de bogue: BUG-000164103
Logiciel: