Bug ID Number |
BUG-000135775 |
Submitted | December 1, 2020 |
Last Modified | June 5, 2024 |
Applies to | ArcGIS for Desktop |
Version found | 10.8.1 |
Operating System | Windows OS |
Operating System Version | 10.0 64 Bit |
Status | Will Not Be Addressed
The development team has considered the issue or request and concluded it will not be addressed. The issue's Additional Information section may contain further explanation.
|
Additional Information
The table used in this workflow does not have a unique, non-null integer field. Thus, an ObjectID is not present. It is possible for other fields like Text and Date to be used as a dynamic ObjectID, but it can still have problems with certain tools. The Export command in ArcMap is one of them. The best approach is to do the following:
1. Create a unique, non-null integer filed on the table. Registering the table with the geodatabase creates an ObjectID field which fulfills that requirement. A geodatabase is not required. Create a field on the table that ArcMap can use as an ObjectID.
2. Use either the Copy Features or Feature Class to Shapefile tools in ArcMap.
3. Use ArcGIS Pro. In ArcGIS Pro, navigate to Data > Export. The Export Features tool runs successfully.
Workaround
Register the feature class with the geodatabase in ArcMap 10.8.1 using SQL 2019.
Steps to Reproduce