BUG-000125149 for ArcGIS Pro

Bug ID Number	BUG-000125149
Submitted	September 11, 2019
Last Modified	April 2, 2025
Applies to	ArcGIS Pro
Version found	2.4.1
Status	Known Limit

Additional Information

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.

Workaround

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.