Bug ID Number |
BUG-000144152 |
Submitted | October 29, 2021 |
Last Modified | February 9, 2025 |
Applies to | ArcGIS Pro |
Version found | 2.8.1 |
Operating System | Windows OS |
Operating System Version | 10.0 64 Bit |
Status | In Product Plan
The issue has been added to the development team's backlog. The goal for issues with this status is to address them in a near-term release (next release or two). Check the issue's Additional Information or Alternate Solution section to see if there is helpful information until it can be fully addressed.
|
Workaround
Workaround #1
- Establish an OLE DB connection from ArcGIS Pro.
- In the Catalog pane, right-click the Databases category and click New OLE DB Connection New Geodatabase Connection.
- On the Insert tab, in the Project group, click the Connections drop-down arrow and click New OLE DB Connection New Geodatabase Connection. The Data Link Properties dialog box appears.
- On the Provider tab, click OLE DB connection for Server. Click Next.
- On the Connection tab, provide the required connection information. Click Test Connection to validate.
- Click OK.
- Add the view to a map and open it.
Workaround #2:
Using the original workflow/data supplied with this defect, modify the query definition of the query layer to select a different unique identifier field (e.g. the RecNo field) instead of the one that is automatically selected. This workaround has only been tested with the original customer's data and workflow.
Steps to Reproduce