Is this expected behavior on 2.6.1? This is VERY DANGEROUS.
Notice what happens…you would expect that the record selected in step #3 would be calculated, i.e. the one currently selected, but it actually calculates the formally selected record, i.e. the selection in step #1.
Solved! Go to Solution.
I created a new FGDB on local C, created new poly feat class with 1 field. Digitized 2 non-overlapping polys.
Same result, the incorrect record is calculated, just like the initial steps.
So, this has nothing to do with the location of the FGDB (local vs. network share)
Win 10 Pro is fully updated, version 2004
Win. control panel, uninstalled Pro, then rebooted.
Clean install 2.6, opened the same Pro project as before, then the same local C:\ FGDB, the problem still persists.
Installed 2.6.1 patch atop 2.6.
Created a new blank project, accessed the same local C:\ FGDB, problem solved
Closed new blank project.
Opened same Pro project as before, then the same local C:\ FGDB, the problem still persists.
Removed all items in geoprocessing history (147 of them), the problem still persists.
Edit: testing continues..
Created new Pro project using an existing template we had.
Had 2 instances of Pro open, the problematic project from above and the new one. I then copy/pasted the Pro map over to the new Project.
In the new project, I now have the original map from the old project. I Field calculated the same local C:\ FGDB, the problem still persists.
Created a new blank map in the new Pro project, I Field calculated the same local C:\ FGDB, problem solved
So, this bug is related to the Pro map, project, which makes sense, because my Collegue and I are working on the "same" project/map. He opened the original and did a SAVE-AS, I'm still using the original.
Edit: finally figured out the bug, it's related to a Hosted Feature Layer being present in the map.
Steps to test attribute calculation:
Steps to Repo the issue with calculating attributes when HFL is present in the map:
Working with Dan directly, I was able to repro this issue. Short story is a hosted feature layer published from Survey 123 Connect and then added to a Map View in ArcGIS Pro will cause this calculation error seen by Dan. I've reported it to Esri Support Services as a BUG. More to come.