When I use the append tool, it's usually part of my ETL process. In that process I have a layer joined with a table that I am appending to another layer. Because of that join, my source layer field names are qualified and look like this - sde.DBO.Ownershiptable.NAME and my target layer field is just NAME. The field mapping component of the append tool doesn't auto match the fields because of the join. I would love it if the append tool looked at just the actual field name instead of the fully qualified field name when auto-matching field names. This could be added to the Environments tab of the tool.
Good one Jeff: I second the idea. Field mapping has always been a tough nut to crack.
Instead of a join, could you use the turbo charge approach from Fairhurst? I use that almost daily it seems: https://community.esri.com/t5/python-blog/turbo-charging-data-manipulation-with-python-cursors-and/b...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.