<?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 Mandatory fields in ArcGIS Collector Questions</title>
    <link>https://community.esri.com/t5/arcgis-collector-questions/mandatory-fields/m-p/86583#M1586</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It would seem that if I define a field for a feature with null values not allowed and host the features in AGOL, Collector populates this (with a space when it's a text field, for example) so the collector can submit without typing anything.. so it sort of defeats the point of not allowing null values. Thoughts?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 29 Jan 2015 12:03:07 GMT</pubDate>
    <dc:creator>PeteCrosier</dc:creator>
    <dc:date>2015-01-29T12:03:07Z</dc:date>
    <item>
      <title>Mandatory fields</title>
      <link>https://community.esri.com/t5/arcgis-collector-questions/mandatory-fields/m-p/86583#M1586</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It would seem that if I define a field for a feature with null values not allowed and host the features in AGOL, Collector populates this (with a space when it's a text field, for example) so the collector can submit without typing anything.. so it sort of defeats the point of not allowing null values. Thoughts?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Jan 2015 12:03:07 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-collector-questions/mandatory-fields/m-p/86583#M1586</guid>
      <dc:creator>PeteCrosier</dc:creator>
      <dc:date>2015-01-29T12:03:07Z</dc:date>
    </item>
    <item>
      <title>Re: Mandatory fields</title>
      <link>https://community.esri.com/t5/arcgis-collector-questions/mandatory-fields/m-p/86584#M1587</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've passed this one on to Esri as I noticed some related weirdness across AGOL and Collector including..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Collector / AGOL - Drop-down fields that don’t allow null values can be left unselected&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AGOL - Drop-down fields that should allow null values are marked as “this value is required”&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AGOL - Auto-populating fields that don't allow null values so the user can submit without typing anything (like Collector), but also letting you remove the auto-added character and storing the feature with no value for the field&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Jan 2015 16:38:47 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-collector-questions/mandatory-fields/m-p/86584#M1587</guid>
      <dc:creator>PeteCrosier</dc:creator>
      <dc:date>2015-01-29T16:38:47Z</dc:date>
    </item>
  </channel>
</rss>

