Select to view content in your preferred language

Issue calculating newly added fields

393
3
10-09-2024 08:55 AM
Labels (1)
TonyaLong
Emerging Contributor

Hi! I just updated my version of Pro from 3.0 to 3.2 a few days ago (our org isn't using 3.3 yet) and since then, the Calculate Field tool fails when I try to calculate values for a newly added field. It gives Error 160327: A column was specified that does not exist. I have a feature view in AGOL that has been exported to a FGDB, downloaded, and added as a database in Pro. I'm working with two shapefiles and a table, and I have this issue on all of them. I even exported a new FGDB and started over in case the original one was corrupt.

In the attached screenshots, you can see a newly added text field in the fields view (New Field.jpg), and then after saving, the column appears in the attribute table (Field in Table.jpg). If I double click in a cell, I can change the value with no problem. However, when I use the Calculate Field tool (Calculate Field.jpg), I get an error message every time (Error Message.jpg). I've also tried just using Calculate Field and specifying a new field name (instead of creating the field first) and I still get the same error message even thought the new field shows up in the table.

The tool works as expected if I calculate an existing field. Even stranger, if I calculate an existing field first and then the new field, it works on the new field. I add and calculate fields regularly to generate reports and I've never had this problem before, but it's been throwing a big wrench into my models that include field calculations. Is there a setting or something new in version 3.2 that I'm missing? Any help would be hugely appreciated - I'm going nuts! 🙃

 

Update: I exported a FGDB of a different feature view created from the same host data and I can add and calculate fields with no problem. So, I tried creating a whole new feature view and exporting that, but got the error message again. I made sure the settings and editing capabilities of both feature views were the same, but there must be something I'm overlooking...

0 Kudos
3 Replies
JM32
by
Frequent Contributor

Maybe try different expression types (python/arcade/SQL/etc) in the Calculate Field tool and see if it tricks it into working...

Otherwise, check to see if you have the latest patch for Pro 3.2 - It looks like there are updates that go to 3.2.4 before it jumps to 3.3, so maybe if you updated to the latest in the 3.2 range it would solve this issue?

 

Hope this helps! 

Jon

TonyaLong
Emerging Contributor

Thanks Jon! Using different expression types didn't help, but I'll definitely look into the patch.

Pukawai
Emerging Contributor

I have run in to similar issues. I suspect that this is due the the reality that PRO IS SLOW and ESRI is constantly trying to speed it up and often with caches: display cache, catalog caches, and probably a host of others. In this case the tool is probably looking at some "not current cache" of the schema containing your featureclass and not finding your new field. If restarting your project solves the problem that is likely the issue, but not very practical in a workflow.

0 Kudos