BUG-000123738 for ArcGIS Pro

Numéro d’ID de bogue	BUG-000123738
Envoi	July 16, 2019
Dernière modification	September 19, 2024
S’applique à	ArcGIS Pro
Version trouvée	2.4
Système d’exploitation	Windows OS
Version du système d’exploitation	10.0 64 Bit
Statut	Known Limit

Informations supplémentaires

This is related to BUG-000125149 and a known limitation. This issue is related to the use of a text field to create a temporary ObjectID field. All tables must have something that uniquely identifies each record. If there is no unique integer column, ArcGIS can generate one on the fly from one or more input columns. However, most queries return an ObjectID that links their results back to the map or table being viewed in ArcGIS. Queries that are passed down to the DBMS have no way of returning the ArcGIS-generated ObjectID. While the query returns accurate results, they cannot be correctly linked back to data in the map. A solution is to add the table as a query layer based on a query that generates an integer ObjectID field by using a windowing function: select isnull(CAST(ROW_NUMBER() OVER(ORDER BY blm_org_cd asc) AS INT),0) AS OBJECTID, blm_org_cd, long_desc, dist_short_nm from dbo.lu_blm_org_cd

Solution de contournement

Place and register the table inside the geodatabase. Creating the table in the geodatabase but not registering it results in the failure of the Select by Attributes tool.
Use ArcMap 10.5.1. if working with a non-geodatabase