I have a dashboard that consumes one feature service (created from Survey123) with 4 copies of it with different filters and different symbology assigned to each. I also have a list in this dashboard.
When I click on a record in the list, everything works fine including a popup that displays with the correct objectID. When I click on this exact same point in the map that is within the dashboard, it shows some random objectID. For example an ID I have in the list is 304, but when I click on it in the map it says 213.
Why would this be the case?
Any ideas Derek Law
Thanks for letting me know Joe. I was not aware of that bug.
Can we push this bug into implementation? Or do you have a workaround? I just need a way to update my feature services and the indicators in my dashboard
Hey Joe!
BUG-000121810 was closed as a "Known Limitation." The ObjectID is changing because when a refresh interval is put on the layer, we convert it into a feature collection to reduce 'flashing' on the screen with each refresh interval. One downside to this is that the ObjectIDs will not be consistent.
As a general rule, we recommend NOT using objectIDs to uniquely identify a feature. Instead, you could use a Global ID or any other field to identify the featue.
Here is a post about how to generate global IDs in Pro.
https://pro.arcgis.com/en/pro-app/tool-reference/data-management/add-global-ids.htm
Hope that helps!
Survey123 forms are edited using objectId, so we HAVE to use objectid to add a Survey123 edit link to a map embedded in a dashboard. Is it possible to use another field to edit a survey in Survey123? If not, then all edit links to Survey123 forms must exist outside of an embedded map.
Exactly. Thanks Malcolm Meyer
Hi Malcolm and Joe,
> Survey123 forms are edited using objectId, so we HAVE to use objectid to add a Survey123 edit link to a map embedded in a dashboard. Is it possible to use another field to edit a survey in Survey123?
I've checked with the Survey123 Dev team and this (bolded text above) will be changing soon. Please see this blog.
Hope this helps,
Ohhhhhhhhh. Well, I wish I would have known this limitation before relying on the ObjectID to be displayed correctly. This limitation has just caused many hours of work to be for nothing and it will completely have to be redone. Is there some way that a warning could be displayed when trying to label based on ObjectID? Of all the fields I am using in my map I was under the impression that ObjectID would be the most consistent and solid only to find that in this case it is total garbage.