nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Batch Updating attributes in Pro

BrandonCraft

I am trying to replace numerous attributes in a target layer from a source layer. The Transfer Attributes tool does exactly what I need on a single polygon at the time, but I need to do it on every record. The target has several fields that are not shared, but I need the rest to update. In our legacy workflow, I would have used an update query in the database itself, but within Pro is there any way to do this? There doesn't seem to be a batch option for this tool.

Encuentra más publicaciones etiquetadas con

Analysis

Geodatabase

Desktop

Accepted answers

All comments

BrandonCraft

Sean, thanks for the answer. It took me a while to get back to this and try it. I had tried this previously with one layer being a linked WFL and the other being in the gdb and it returned all null values during the paste, updating the attribute table to all nulls. I just tried it again now that both layers are in the gdb, and it did the same thing. There is a schema difference, but the fields in common are named and formatted identically. It did not offer a field mapping option during the process. Not sure what is going on there.

Anonymous User

Try copy/paste attributes in the attributes pane.

select the source feature, right-click the feature in the attributes pane and select 'copy attributes'
select the target features (can use select all in the layer context menu in the table of contents).
right-click the target layer in the attributes pane and select 'paste attributes'

this procedure will use a field map like the attribute transfer tool

BrandonCraft

It is the output from several different pieces of enterprise software. Yes, we all understand each field, and each field is used by numerous people. Different industries have very different schema, but that many fields is not uncommon in forestry at all. The schema come from the client, so we have very little input into how they are designed, but in this case it is a very reasonable setup given the needs placed on the data. Even on other datasets where there are more, a good data dictionary goes a long way.

JoeBorgione

...whole team can use and understand though...

114 fields? Your team uses and understands all 114 fields? Good on ya!

BrandonCraft

I agree Joe, but given that this is 114 fields on thousands of records just in this one example (more on other datasets), I probably need something the whole team can use and understand though. I would still like to find a more elegant solution. I'll update here if I find something.

jcarlson

I mean, the batch field calculator really wouldn't even need the join in place if the expression were written correctly. But I'll have to give it a shot next time a situation comes up that might need it. I'll never learn how to use the arcpy cursors if I keep avoiding them...

JoeBorgione

The whole point of the dictionary approach is to avoid a join. I done it dozens of times on thousands of records/updates. But do what you feel works for you.

BrandonCraft

I haven't tried that since I moved them both into the same gdb, but the other day I tried doing it while one was a WFL, and it hard crashed Pro. I hadn't thought to try it again since I moved things around though. Good thinking.

jcarlson

Ah, boo. It would be a fairly simple matter if you could take advantage of Spatially Enabled DataFrames, but I try to stay away from ArcPy cursors as much as I can, we don't get along.

Do the records in your two tables line up on an attribute?

Could you: Create an ad-hoc join → batch field calculate the target attributes → remove the join?

BrandonCraft

I'm working locally. Both layers are in a file geodatabase. When we used Personal Geodatabases, I would have just written an update query in Access. I am still developing the new processes, and this is one of the only issues left.

I am fairly certain it will have to be written in Python, but it just seems like there would be a pre-built tool for it.

jcarlson

Are the layers accessible via a Service, or are you working locally on file-based resources? The ArcGIS Python API may be helpful here, but mainly if you can take advantage of the edit_features function on a feature service.

BrandonCraft

Joe,

Python is definitely an option, but I was struggling to figure out how to go about it. Thanks for responding. That dictionary method could work, but the number of fields would make it pretty laborious. With other tools previously, I have modified them to run as a batch, but for some reason this one doesn't seem to do that.

JoeBorgione

Is python an option? I use a dictionary approach described here.

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.