| 不具合 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.
再現の手順