| 漏洞 ID 编号 |
BUG-000125149 |
| 已提交 | September 11, 2019 |
| 上次修改时间 | April 2, 2025 |
| 适用范围 | ArcGIS Pro |
| 找到的版本 | 2.4.1 |
| 状态 | Known Limit
经开发团队审核,已确定此问题与不受 Esri 控制的软件的已知限制有关。 问题的“其他信息”部分可能包含进一步说明。
|
附加信息
This issue is related to the use of multiple columns to create a temporary ObjectID field. All tables must have something that uniquely identifies each record. If there is no unique column ArcGIS Pro can generate one on the fly from multiple input columns. However, most queries return an ObjectID that links their results back to the map or table being viewed in ArcGIS Pro. Queries that are passed down to the DBMS are unable to return the ArcGIS-generated ObjectID. While the query returns accurate results, they cannot be correctly linked back to data in the map.
解决办法
Use one of the following workarounds:
- Create a composite column in the query defining the query layer.
If COL1, COL2, COL3 & COL4 are used in combination to create a unique identifier, concatenate them into a new columns:select CAST(CONCAT(COL1, COL2, COL3, COL4) as int) as ObjectID,COL1, COL2, COL3, COL4, ALL, THE, REST, OF, MY, COLUMNS from MYDB.dbo.MYTABLEThis generates a new column 'ObjectID' and attribute queries are able to return correct values.
- Register the table with the geodatabase before running the select by attribute query.
重现步骤