<?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 Support fields that require unique values in Collector app in ArcGIS Collector Ideas</title>
    <link>https://community.esri.com/t5/arcgis-collector-ideas/support-fields-that-require-unique-values-in/idi-p/950385</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It would be great to be able to use fields that require unique values in the Collector app.&amp;nbsp; We are editing a streetlight poles dataset in the field using Collector, and each pole has a unique PoleID.&amp;nbsp; New poles that are added get assigned a new PoleID (by the person manually at this time as auto-number fields are not supported by Collector either).&amp;nbsp; They have a system for assigning numbers but&amp;nbsp;occasionally we get duplicates.&amp;nbsp; It would be helpful if we could constrain the field to only allow unique values within the Collector app.&amp;nbsp; If we set&amp;nbsp;up an index on the feature class in ArcCatalog that only allows unique values it works great in ArcGIS Desktop but is not supported by Collector.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 24 Nov 2016 22:44:58 GMT</pubDate>
    <dc:creator>StephanieBlazey</dc:creator>
    <dc:date>2016-11-24T22:44:58Z</dc:date>
    <item>
      <title>Support fields that require unique values in Collector app</title>
      <link>https://community.esri.com/t5/arcgis-collector-ideas/support-fields-that-require-unique-values-in/idi-p/950385</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It would be great to be able to use fields that require unique values in the Collector app.&amp;nbsp; We are editing a streetlight poles dataset in the field using Collector, and each pole has a unique PoleID.&amp;nbsp; New poles that are added get assigned a new PoleID (by the person manually at this time as auto-number fields are not supported by Collector either).&amp;nbsp; They have a system for assigning numbers but&amp;nbsp;occasionally we get duplicates.&amp;nbsp; It would be helpful if we could constrain the field to only allow unique values within the Collector app.&amp;nbsp; If we set&amp;nbsp;up an index on the feature class in ArcCatalog that only allows unique values it works great in ArcGIS Desktop but is not supported by Collector.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 Nov 2016 22:44:58 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-collector-ideas/support-fields-that-require-unique-values-in/idi-p/950385</guid>
      <dc:creator>StephanieBlazey</dc:creator>
      <dc:date>2016-11-24T22:44:58Z</dc:date>
    </item>
    <item>
      <title>Re: Support fields that require unique values in Collector app</title>
      <link>https://community.esri.com/t5/arcgis-collector-ideas/support-fields-that-require-unique-values-in/idc-p/950386#M764</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Why have a user enter this at all? You might consider post-processing this until a version of "attribute assistant" is available for the arcgis platform. There are bigger problems when considering the potential for multiple users and the possibility of disconnected states in Collector/Mobile. We have the same problem with sde geodatabase unique fields as they are not supported in a multi-user environment so the only solution for us has been attribute assistant and/or post processing the generation of the ID's.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 28 Nov 2016 21:58:46 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-collector-ideas/support-fields-that-require-unique-values-in/idc-p/950386#M764</guid>
      <dc:creator>RonnieRichards</dc:creator>
      <dc:date>2016-11-28T21:58:46Z</dc:date>
    </item>
  </channel>
</rss>

