<?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>topic Re: Changing Feature Classes Schema in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/changing-feature-classes-schema/m-p/1184324#M44079</link>
    <description>&lt;P&gt;I name my tables with a numeric suffix (e.g., "project_stuff_t1") so I can make later changes ("project_stuff_t2") and keep track things like type changes.&amp;nbsp; This often manifests with revised service names ("proj_data_10" -&amp;gt; "proj_data_11" or "proj_data_20", depending on scope changes), allowing the "old" service to run while dashboards are updated to use the new service.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Of course, to pull this off, you don't modify the table, but create a new one from the old before archiving the old content and dropping it.&lt;/P&gt;&lt;P&gt;- V&lt;/P&gt;</description>
    <pubDate>Mon, 20 Jun 2022 14:46:48 GMT</pubDate>
    <dc:creator>VinceAngelo</dc:creator>
    <dc:date>2022-06-20T14:46:48Z</dc:date>
    <item>
      <title>Changing Feature Classes Schema</title>
      <link>https://community.esri.com/t5/data-management-questions/changing-feature-classes-schema/m-p/1184295#M44078</link>
      <description>&lt;P&gt;What is the best way to change schema for feature classes in the Enterprise Geodatabase? We are going through reorganizing of our data and part of it includes streamlining the schema (field names) for our feature classes. The challenge is, a lot of these feature classes have been published on the ArcGIS Server and are currently being used in web applications.&lt;/P&gt;&lt;P&gt;Is there a way for me to modify the schema without breaking the connection to the web apps?&lt;/P&gt;</description>
      <pubDate>Mon, 20 Jun 2022 13:14:36 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/changing-feature-classes-schema/m-p/1184295#M44078</guid>
      <dc:creator>aam</dc:creator>
      <dc:date>2022-06-20T13:14:36Z</dc:date>
    </item>
    <item>
      <title>Re: Changing Feature Classes Schema</title>
      <link>https://community.esri.com/t5/data-management-questions/changing-feature-classes-schema/m-p/1184324#M44079</link>
      <description>&lt;P&gt;I name my tables with a numeric suffix (e.g., "project_stuff_t1") so I can make later changes ("project_stuff_t2") and keep track things like type changes.&amp;nbsp; This often manifests with revised service names ("proj_data_10" -&amp;gt; "proj_data_11" or "proj_data_20", depending on scope changes), allowing the "old" service to run while dashboards are updated to use the new service.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Of course, to pull this off, you don't modify the table, but create a new one from the old before archiving the old content and dropping it.&lt;/P&gt;&lt;P&gt;- V&lt;/P&gt;</description>
      <pubDate>Mon, 20 Jun 2022 14:46:48 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/changing-feature-classes-schema/m-p/1184324#M44079</guid>
      <dc:creator>VinceAngelo</dc:creator>
      <dc:date>2022-06-20T14:46:48Z</dc:date>
    </item>
  </channel>
</rss>

