<?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 Do not replace existing values of indexed integer field with new OID values when converting a table to XY feature class in ArcGIS Pro Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pro-ideas/do-not-replace-existing-values-of-indexed-integer/idi-p/1520772</link>
    <description>&lt;P&gt;Please do not remove an indexed integer field and replace it with a new ObjectID field when converting a table of X/Y coordinates to a feature class.&amp;nbsp; In ArcPro 3.3.1, this is occurring and data is lost.&amp;nbsp; Thank you.&lt;/P&gt;</description>
    <pubDate>Tue, 13 Aug 2024 18:36:00 GMT</pubDate>
    <dc:creator>GaryBilotta</dc:creator>
    <dc:date>2024-08-13T18:36:00Z</dc:date>
    <item>
      <title>Do not replace existing values of indexed integer field with new OID values when converting a table to XY feature class</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/do-not-replace-existing-values-of-indexed-integer/idi-p/1520772</link>
      <description>&lt;P&gt;Please do not remove an indexed integer field and replace it with a new ObjectID field when converting a table of X/Y coordinates to a feature class.&amp;nbsp; In ArcPro 3.3.1, this is occurring and data is lost.&amp;nbsp; Thank you.&lt;/P&gt;</description>
      <pubDate>Tue, 13 Aug 2024 18:36:00 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/do-not-replace-existing-values-of-indexed-integer/idi-p/1520772</guid>
      <dc:creator>GaryBilotta</dc:creator>
      <dc:date>2024-08-13T18:36:00Z</dc:date>
    </item>
    <item>
      <title>Re: Do not replace existing values of indexed integer field with new OID values when converting a table to XY feature class</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/do-not-replace-existing-values-of-indexed-integer/idc-p/1520940#M31541</link>
      <description>&lt;P&gt;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/33423"&gt;@GaryBilotta&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Could you please reach out to Esri Support and have an support ticket opened for this? Did it work before?&lt;/P&gt;</description>
      <pubDate>Tue, 13 Aug 2024 23:28:20 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/do-not-replace-existing-values-of-indexed-integer/idc-p/1520940#M31541</guid>
      <dc:creator>TanuHoque</dc:creator>
      <dc:date>2024-08-13T23:28:20Z</dc:date>
    </item>
    <item>
      <title>Re: Do not replace existing values of indexed integer field with new OID values when converting a table to XY feature class - Status changed to: Closed</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/do-not-replace-existing-values-of-indexed-integer/idc-p/1526419#M31722</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/33423"&gt;@GaryBilotta&lt;/a&gt;&amp;nbsp;If you are running a workflow where data is lost as you are describing, that should not be submitted as an idea. Please &lt;A href="https://support.esri.com/en-us/contact" target="_self"&gt;contact technical support&lt;/A&gt; to investigate. Thank you.&lt;/P&gt;</description>
      <pubDate>Fri, 23 Aug 2024 14:02:50 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/do-not-replace-existing-values-of-indexed-integer/idc-p/1526419#M31722</guid>
      <dc:creator>KoryKramer</dc:creator>
      <dc:date>2024-08-23T14:02:50Z</dc:date>
    </item>
  </channel>
</rss>

