<?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 v3 is evaluating constraints on fields that are not relevant yet in ArcGIS Survey123 Questions</title>
    <link>https://community.esri.com/t5/arcgis-survey123-questions/v3-is-evaluating-constraints-on-fields-that-are/m-p/875133#M29054</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a form that was in use for 6+ months now without issue.&amp;nbsp; I updated to v3, made&amp;nbsp;a small change and republished.&amp;nbsp; The form then suddenly starting stopping submissions giving a error that a constraint was being broken, on a field that was not even relevant at the time and the user cannot even see.&amp;nbsp; I had to&amp;nbsp;add "" empty string now to the constraint to get around it.&amp;nbsp; Always worked as designed before.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this a new&amp;nbsp;bug?&amp;nbsp; Why would a constraint be checked on a non-relevant field?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 16 Aug 2018 17:38:16 GMT</pubDate>
    <dc:creator>DougBrowning</dc:creator>
    <dc:date>2018-08-16T17:38:16Z</dc:date>
    <item>
      <title>v3 is evaluating constraints on fields that are not relevant yet</title>
      <link>https://community.esri.com/t5/arcgis-survey123-questions/v3-is-evaluating-constraints-on-fields-that-are/m-p/875133#M29054</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a form that was in use for 6+ months now without issue.&amp;nbsp; I updated to v3, made&amp;nbsp;a small change and republished.&amp;nbsp; The form then suddenly starting stopping submissions giving a error that a constraint was being broken, on a field that was not even relevant at the time and the user cannot even see.&amp;nbsp; I had to&amp;nbsp;add "" empty string now to the constraint to get around it.&amp;nbsp; Always worked as designed before.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this a new&amp;nbsp;bug?&amp;nbsp; Why would a constraint be checked on a non-relevant field?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Aug 2018 17:38:16 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-survey123-questions/v3-is-evaluating-constraints-on-fields-that-are/m-p/875133#M29054</guid>
      <dc:creator>DougBrowning</dc:creator>
      <dc:date>2018-08-16T17:38:16Z</dc:date>
    </item>
    <item>
      <title>Re: v3 is evaluating constraints on fields that are not relevant yet</title>
      <link>https://community.esri.com/t5/arcgis-survey123-questions/v3-is-evaluating-constraints-on-fields-that-are/m-p/875134#M29055</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Doug&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are you able to share your survey xls? I'll take a look.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;John&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 20 Aug 2018 01:04:18 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-survey123-questions/v3-is-evaluating-constraints-on-fields-that-are/m-p/875134#M29055</guid>
      <dc:creator>JohnathanHasthorpe</dc:creator>
      <dc:date>2018-08-20T01:04:18Z</dc:date>
    </item>
  </channel>
</rss>

