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; } } }

Append tool not honoring common fields

MKF62

I am using a FGDB feature class that has a field called "MgmtTractID" of string type. It has the exact same properties and name as a field in my feature class in an SDE geodatabase. Unfortunately, the attributes from MgmtTractID in my FGDB will not transfer to the SDE MgmtTractID field. I'm not sure why, if I use the Append tool (with selections on my FGDB feature class) in the GUI, it works fine. I use "NO_TEST" because some of the fields aren't common between the two feature classes. I have also checked with a search cursor that my feature layer contains the values I would like to transfer.

arcpy<SPAN class="punctuation token">.</SPAN>Append_management<SPAN class="punctuation token">(</SPAN>mgmtTractFL<SPAN class="punctuation token">,</SPAN> db_mgmtTractFC<SPAN class="punctuation token">,</SPAN> <SPAN class="string token">'NO_TEST'</SPAN><SPAN class="punctuation token">)</SPAN>‍<SPAN class="line-numbers-rows"><SPAN>‍</SPAN></SPAN>

The documentation for the Append tool states this:

Map layers can be used as Input Datasets. If a layer has a selection, only the selected records (features or table rows) are used by the Append tool.

So why doesn't it work?

Find more posts tagged with

Accepted answers

MKF62

So I had assumed that when you use "NO_TEST" it would default to using whatever common fields are there. Turns out you have to actually use field map objects. So this is what I ended up with:

fieldmap <SPAN class="operator token">=</SPAN> arcpy<SPAN class="punctuation token">.</SPAN>FieldMappings<SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">)</SPAN>
fieldmap<SPAN class="punctuation token">.</SPAN>addTable<SPAN class="punctuation token">(</SPAN>db_mgmtTractFC<SPAN class="punctuation token">)</SPAN>
fieldmap<SPAN class="punctuation token">.</SPAN>addTable<SPAN class="punctuation token">(</SPAN>mgmtTractFL<SPAN class="punctuation token">)</SPAN>
fieldmap<SPAN class="punctuation token">.</SPAN>removeAll<SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">)</SPAN>
fm_TractID <SPAN class="operator token">=</SPAN> arcpy<SPAN class="punctuation token">.</SPAN>FieldMap<SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">)</SPAN>
fm_TractID<SPAN class="punctuation token">.</SPAN>addInputField<SPAN class="punctuation token">(</SPAN>db_mgmtTractFC<SPAN class="punctuation token">,</SPAN> <SPAN class="string token">"MgmtTractID"</SPAN><SPAN class="punctuation token">)</SPAN>
<SPAN class="comment token">#I had a joined table,so I had to specify the field by putting the name of </SPAN>
<SPAN class="comment token">#the layer at the beginning of the field name</SPAN>
fm_TractID<SPAN class="punctuation token">.</SPAN>addInputField<SPAN class="punctuation token">(</SPAN>mgmtTractFL<SPAN class="punctuation token">,</SPAN> <SPAN class="string token">"AL_MgmtTracts_Template.MgmtTractID"</SPAN><SPAN class="punctuation token">)</SPAN>
fieldmap<SPAN class="punctuation token">.</SPAN>addFieldMap<SPAN class="punctuation token">(</SPAN>fm_TractID<SPAN class="punctuation token">)</SPAN>
arcpy<SPAN class="punctuation token">.</SPAN>Append_management<SPAN class="punctuation token">(</SPAN>mgmtTractFL<SPAN class="punctuation token">,</SPAN> db_mgmtTractFC<SPAN class="punctuation token">,</SPAN> <SPAN class="string token">'NO_TEST'</SPAN><SPAN class="punctuation token">,</SPAN> fieldmap<SPAN class="punctuation token">)</SPAN><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

All comments

dougbrowning

NO_TEST always brought over the common fields just fine for me. I use it a lot actually. I am trying to remember if a Join messed it up.

MKF62

Field mapping is super confusing in arcpy. It took me a while to figure it out switching back and forth between the FieldMappings and FieldMap help documents.

JoeBorgione

I started to reply to your original post, but when I posted, you'd already deleted it. So I'll try again now...

I take it you are using a feature layer, mgmtTractFL because you've made a selection via a script, right? And you mentioned it worked with the tool interface but not with arcpy.Append_management. When it is successful with the tool are you using the feature layer, or the actual feature class? It does seem odd, indeed....

I'll see if I can replicate the problem here locally with something on hand....

hahaha. now you've beaten me to the punch again! Good job on using field mapping. I've never had that work for me, and I've never known anyone to get it to work!

MKF62

So I had assumed that when you use "NO_TEST" it would default to using whatever common fields are there. Turns out you have to actually use field map objects. So this is what I ended up with:

fieldmap <SPAN class="operator token">=</SPAN> arcpy<SPAN class="punctuation token">.</SPAN>FieldMappings<SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">)</SPAN>
fieldmap<SPAN class="punctuation token">.</SPAN>addTable<SPAN class="punctuation token">(</SPAN>db_mgmtTractFC<SPAN class="punctuation token">)</SPAN>
fieldmap<SPAN class="punctuation token">.</SPAN>addTable<SPAN class="punctuation token">(</SPAN>mgmtTractFL<SPAN class="punctuation token">)</SPAN>
fieldmap<SPAN class="punctuation token">.</SPAN>removeAll<SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">)</SPAN>
fm_TractID <SPAN class="operator token">=</SPAN> arcpy<SPAN class="punctuation token">.</SPAN>FieldMap<SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">)</SPAN>
fm_TractID<SPAN class="punctuation token">.</SPAN>addInputField<SPAN class="punctuation token">(</SPAN>db_mgmtTractFC<SPAN class="punctuation token">,</SPAN> <SPAN class="string token">"MgmtTractID"</SPAN><SPAN class="punctuation token">)</SPAN>
<SPAN class="comment token">#I had a joined table,so I had to specify the field by putting the name of </SPAN>
<SPAN class="comment token">#the layer at the beginning of the field name</SPAN>
fm_TractID<SPAN class="punctuation token">.</SPAN>addInputField<SPAN class="punctuation token">(</SPAN>mgmtTractFL<SPAN class="punctuation token">,</SPAN> <SPAN class="string token">"AL_MgmtTracts_Template.MgmtTractID"</SPAN><SPAN class="punctuation token">)</SPAN>
fieldmap<SPAN class="punctuation token">.</SPAN>addFieldMap<SPAN class="punctuation token">(</SPAN>fm_TractID<SPAN class="punctuation token">)</SPAN>
arcpy<SPAN class="punctuation token">.</SPAN>Append_management<SPAN class="punctuation token">(</SPAN>mgmtTractFL<SPAN class="punctuation token">,</SPAN> db_mgmtTractFC<SPAN class="punctuation token">,</SPAN> <SPAN class="string token">'NO_TEST'</SPAN><SPAN class="punctuation token">,</SPAN> fieldmap<SPAN class="punctuation token">)</SPAN><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

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