I want to use Locate to search on objectid (or any other way someone can suggest). When I go to configure the layer for Locate, the objectid field is not listed. Any suggestions would be appreciated.
We have the issue of not being able to search the OBJECTID in Field Maps (Portal, not ArcGIS Online). Does anyone have suggestions of other threads or just in general on that?
Yeah, it seems kind of strange to output a table of object IDs, but not allow users to search for those object IDs using the Locate tool.
We used to be able to search OBJECTID in ArcMap, why in the world did you take this functionality away in Pro?
Why can I run the "Find Identical" tool using the SHAPE field which then dumps out a table with IN_FID? The IN_FID is the OBJECTID of the original data for which I am trying to find duplicated objects! So therefore I want to use my "search layer window" to quickly go to each identical object and figure out which one I want to delete, but I can't. Instead I am forced to Join my data by OBJECTID to IN_FID and we all know how slow joined data can be...
In case anyone is still seeking the answer for this. This would address it: https://community.esri.com/t5/arcgis-online-questions/enable-objectid-field-for-find-locations-and-web/td-p/698504
Searching for the objectID is certainly required at times for me too - within the webapp builder you can configure the search widget to search for the objectID field.
Although I agree with your statement overall, I don't think it is applicable here. The fact is that Esri has put meaning to the FID/OID/OBJECTID field. When troubleshooting certain kinds of data issues, especially as they pertain to errors generated from Esri geoprocessing tools, using OID to track down a record is both handy and relevant.
I don't think this issue is related to using the OID in relationship classes.
I think it is generally considered bad practice to treat the objectid field as a unique primary or foreign key when querying tables, as the objectid column may not persist and/or the values may be updated when transforming the data in various GP tools.
More info from GIS Stack Exchange: When is it safe to use ObjectIDs as keys in a relationship class?
So every time the OID is updated (say, add a new feature), you'd have to perform this calculation again. I'm with Randy, sometimes, especially when looking at data issues (e.g. failed edits, etc...), objectid is the only thing you have to go on.
Thanks for the reply Robert. Find myself regularly searching on objectid when digging into people's data issues, so having a search available for objectid is handy. I'll use your suggestion for now but hope they add it later as adding a field to all feature classes to do an objectid search would be a little cumbersome, especially since the objectid is already there. Thanks again for your quick response. Look forward to continuing to learn Pro.
Randy - it would seem that all ArcGIS maintained fields for the Configure Layer for Locate options are missing. You could add a new field to your feature class attribute table and calculate the new field by the ObjectID. Then you could configure the Locate to search on that field.
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
