<?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: Relevance inside group circumvents required field in ArcGIS Survey123 Questions</title>
    <link>https://community.esri.com/t5/arcgis-survey123-questions/relevance-inside-group-circumvents-required-field/m-p/855137#M24575</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Erika,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I believe the issue you are describing above has been fixed in our upcoming 3.5 release, which will ship at the end of this week. Please keep an eye out for it, and test with latest version and let us know if you still have any issues.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you want to test it out earlier, we have the 3.5 RC builds available on EAC for testing:&amp;nbsp;&lt;A href="https://earlyadopter.esri.com/project/forum/default.html?cap=e69ef91f45744b98882c651f7b518eb7"&gt;https://earlyadopter.esri.com/project/forum/default.html?cap=e69ef91f45744b98882c651f7b518eb7&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phil.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 24 Jun 2019 23:30:43 GMT</pubDate>
    <dc:creator>Anonymous User</dc:creator>
    <dc:date>2019-06-24T23:30:43Z</dc:date>
    <item>
      <title>Relevance inside group circumvents required field</title>
      <link>https://community.esri.com/t5/arcgis-survey123-questions/relevance-inside-group-circumvents-required-field/m-p/855136#M24574</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a field that's required.&amp;nbsp; It's inside a group that has relevance set on the basis of a previous question having a value.&lt;/P&gt;&lt;P&gt;I also have a relevant statement set on the question itself.&amp;nbsp; When I do this, even though the field is required, and is relevant, the form allows me to submit it without filling out this question.&amp;nbsp; This seems like a bug.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm using Survey123 Connect 3.3.51 and Survey123 for iOS version 3.3.64.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I made a simple survey to demonstrate. I've attached it below.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Jun 2019 23:19:14 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-survey123-questions/relevance-inside-group-circumvents-required-field/m-p/855136#M24574</guid>
      <dc:creator>JakeJacobs</dc:creator>
      <dc:date>2019-06-24T23:19:14Z</dc:date>
    </item>
    <item>
      <title>Re: Relevance inside group circumvents required field</title>
      <link>https://community.esri.com/t5/arcgis-survey123-questions/relevance-inside-group-circumvents-required-field/m-p/855137#M24575</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Erika,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I believe the issue you are describing above has been fixed in our upcoming 3.5 release, which will ship at the end of this week. Please keep an eye out for it, and test with latest version and let us know if you still have any issues.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you want to test it out earlier, we have the 3.5 RC builds available on EAC for testing:&amp;nbsp;&lt;A href="https://earlyadopter.esri.com/project/forum/default.html?cap=e69ef91f45744b98882c651f7b518eb7"&gt;https://earlyadopter.esri.com/project/forum/default.html?cap=e69ef91f45744b98882c651f7b518eb7&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Phil.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Jun 2019 23:30:43 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-survey123-questions/relevance-inside-group-circumvents-required-field/m-p/855137#M24575</guid>
      <dc:creator>Anonymous User</dc:creator>
      <dc:date>2019-06-24T23:30:43Z</dc:date>
    </item>
  </channel>
</rss>

