<?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 Modify fields after a hosted feature service is created - Independently select fields as required. in ArcGIS Online Ideas</title>
    <link>https://community.esri.com/t5/arcgis-online-ideas/modify-fields-after-a-hosted-feature-service-is/idi-p/939967</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I know that required fields are set by not allowing null values, but this is not exactly an easy operation to perform after a layer is created. It's often not a best practice to export a feature class' schema, changing the properties, then importing the features into the new schema. It can change ID's and cause unforeseen issues.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My suggestion is to implement a property in ArcGIS Online that allows the administrator to set field requirements in the application independently of the feature classes properties. Helpful for administrators to specify which fields NEED to be collected in the field using ArcGIS Collector, without having to make adjustments to the feature class' properties.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 05 Jun 2015 13:46:06 GMT</pubDate>
    <dc:creator>ErikEngstrom</dc:creator>
    <dc:date>2015-06-05T13:46:06Z</dc:date>
    <item>
      <title>Modify fields after a hosted feature service is created - Independently select fields as required.</title>
      <link>https://community.esri.com/t5/arcgis-online-ideas/modify-fields-after-a-hosted-feature-service-is/idi-p/939967</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I know that required fields are set by not allowing null values, but this is not exactly an easy operation to perform after a layer is created. It's often not a best practice to export a feature class' schema, changing the properties, then importing the features into the new schema. It can change ID's and cause unforeseen issues.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My suggestion is to implement a property in ArcGIS Online that allows the administrator to set field requirements in the application independently of the feature classes properties. Helpful for administrators to specify which fields NEED to be collected in the field using ArcGIS Collector, without having to make adjustments to the feature class' properties.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Jun 2015 13:46:06 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-online-ideas/modify-fields-after-a-hosted-feature-service-is/idi-p/939967</guid>
      <dc:creator>ErikEngstrom</dc:creator>
      <dc:date>2015-06-05T13:46:06Z</dc:date>
    </item>
    <item>
      <title>Re: Modify fields after a hosted feature service is created - Independently select fields as required.</title>
      <link>https://community.esri.com/t5/arcgis-online-ideas/modify-fields-after-a-hosted-feature-service-is/idc-p/939968#M2822</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Great idea, of course if the feature class requires the field than that could be locked as required but most of the time that is not the issue.

&lt;!-- content transformation source ID: 00aE000000C6h86 --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Jun 2015 15:07:46 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-online-ideas/modify-fields-after-a-hosted-feature-service-is/idc-p/939968#M2822</guid>
      <dc:creator>JoshWhite</dc:creator>
      <dc:date>2015-06-05T15:07:46Z</dc:date>
    </item>
    <item>
      <title>Re: Modify fields after a hosted feature service is created - Independently select fields as required.</title>
      <link>https://community.esri.com/t5/arcgis-online-ideas/modify-fields-after-a-hosted-feature-service-is/idc-p/939969#M2823</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;If you havnt seen this you can change things like these in the Admin of the Rest service.&lt;BR /&gt;&lt;BR /&gt;Updating Hosted Feature Services in ArcGIS Online&lt;BR /&gt;&lt;A href="https://blogs.esri.com/esri/arcgis/2014/10/19/updating-hosted-feature-services-in-arcgis-online/" target="_blank"&gt;https://blogs.esri.com/esri/arcgis/2014/10/19/updating-hosted-feature-services-in-arcgis-online/&lt;/A&gt;&lt;BR /&gt;Here is a document that shows you&amp;nbsp;&lt;A href="http://blogs.esri.com/esri/arcgis/files/2014/10/How-to-Update-Hosted-Feature-Service-Schemas1.pdf" target="_blank"&gt;&lt;FONT color="#0066cc"&gt;How to Update Hosted Feature Service Schemas&lt;/FONT&gt;&lt;/A&gt;&lt;BR /&gt;&amp;nbsp;

&lt;!-- content transformation source ID: 00aE000000GvtgS --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Feb 2016 15:48:41 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-online-ideas/modify-fields-after-a-hosted-feature-service-is/idc-p/939969#M2823</guid>
      <dc:creator>DamonEisenach</dc:creator>
      <dc:date>2016-02-10T15:48:41Z</dc:date>
    </item>
    <item>
      <title>Re: Modify fields after a hosted feature service is created - Independently select fields as required. - Status changed to: Implemented</title>
      <link>https://community.esri.com/t5/arcgis-online-ideas/modify-fields-after-a-hosted-feature-service-is/idc-p/1644946#M13190</link>
      <description>&lt;P&gt;Field Maps Designer allows fields to be selected as 'required' for field data collection using the Field Maps mobile app. This appears to fulfill the requirements of this idea.&lt;/P&gt;</description>
      <pubDate>Fri, 22 Aug 2025 22:23:24 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-online-ideas/modify-fields-after-a-hosted-feature-service-is/idc-p/1644946#M13190</guid>
      <dc:creator>ScottBall</dc:creator>
      <dc:date>2025-08-22T22:23:24Z</dc:date>
    </item>
  </channel>
</rss>

