<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>idea Field matching in Field Mapping for the Append geoprocessing tool. in ArcGIS Pro Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pro-ideas/field-matching-in-field-mapping-for-the-append/idi-p/1004047</link>
    <description>&lt;P&gt;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.&lt;/P&gt;</description>
    <pubDate>Mon, 23 Nov 2020 18:06:52 GMT</pubDate>
    <dc:creator>JeffWard</dc:creator>
    <dc:date>2020-11-23T18:06:52Z</dc:date>
    <item>
      <title>Field matching in Field Mapping for the Append geoprocessing tool.</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/field-matching-in-field-mapping-for-the-append/idi-p/1004047</link>
      <description>&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Mon, 23 Nov 2020 18:06:52 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/field-matching-in-field-mapping-for-the-append/idi-p/1004047</guid>
      <dc:creator>JeffWard</dc:creator>
      <dc:date>2020-11-23T18:06:52Z</dc:date>
    </item>
    <item>
      <title>Re: Field matching in Field Mapping for the Append geoprocessing tool.</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/field-matching-in-field-mapping-for-the-append/idc-p/1004060#M14385</link>
      <description>&lt;P&gt;Good one Jeff: I second the idea.&amp;nbsp; Field mapping has always been a tough nut to crack.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Instead of a join, could you use the turbo charge approach from Fairhurst?&amp;nbsp; I use that almost daily it seems:&amp;nbsp;&amp;nbsp;&lt;A href="https://community.esri.com/t5/python-blog/turbo-charging-data-manipulation-with-python-cursors-and/ba-p/884079" target="_blank"&gt;https://community.esri.com/t5/python-blog/turbo-charging-data-manipulation-with-python-cursors-and/ba-p/884079&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 23 Nov 2020 18:47:49 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/field-matching-in-field-mapping-for-the-append/idc-p/1004060#M14385</guid>
      <dc:creator>JoeBorgione</dc:creator>
      <dc:date>2020-11-23T18:47:49Z</dc:date>
    </item>
  </channel>
</rss>

