<?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: Required based on a previous response in ArcGIS Survey123 Questions</title>
    <link>https://community.esri.com/t5/arcgis-survey123-questions/required-based-on-a-previous-response/m-p/794422#M9069</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No problems!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On the feedback, we are getting a lot of interest from our field teams around repeats. The ability to pre-fill data in them, to generate summary statistics from them, things like that.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 13 Apr 2017 05:55:54 GMT</pubDate>
    <dc:creator>DanielMcIlroy</dc:creator>
    <dc:date>2017-04-13T05:55:54Z</dc:date>
    <item>
      <title>Required based on a previous response</title>
      <link>https://community.esri.com/t5/arcgis-survey123-questions/required-based-on-a-previous-response/m-p/794420#M9067</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just wondering if it is possible to make a question required based on a previous response?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My example is that field teams may be collecting a duplicate sample to be sent to a different lab for analysis. For this duplicate, they would fill in the sample ID (linking it to the original sample), but would answer a question stating that this was a QC duplicate which would in turn make a range of questions that were previously mandatory no longer mandatory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I could go through and make all of these fields linked to the initial duplicate Y/N question via the relevant column, but was wondering if there was a way to do this in the required field.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;Dan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Apr 2017 05:44:28 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-survey123-questions/required-based-on-a-previous-response/m-p/794420#M9067</guid>
      <dc:creator>DanielMcIlroy</dc:creator>
      <dc:date>2017-04-13T05:44:28Z</dc:date>
    </item>
    <item>
      <title>Re: Required based on a previous response</title>
      <link>https://community.esri.com/t5/arcgis-survey123-questions/required-based-on-a-previous-response/m-p/794421#M9068</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Not possible at the moment, but definitively in our road map! Thanks for the feedback and&amp;nbsp; details on the use case!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Apr 2017 05:46:19 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-survey123-questions/required-based-on-a-previous-response/m-p/794421#M9068</guid>
      <dc:creator>IsmaelChivite</dc:creator>
      <dc:date>2017-04-13T05:46:19Z</dc:date>
    </item>
    <item>
      <title>Re: Required based on a previous response</title>
      <link>https://community.esri.com/t5/arcgis-survey123-questions/required-based-on-a-previous-response/m-p/794422#M9069</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No problems!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On the feedback, we are getting a lot of interest from our field teams around repeats. The ability to pre-fill data in them, to generate summary statistics from them, things like that.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Apr 2017 05:55:54 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-survey123-questions/required-based-on-a-previous-response/m-p/794422#M9069</guid>
      <dc:creator>DanielMcIlroy</dc:creator>
      <dc:date>2017-04-13T05:55:54Z</dc:date>
    </item>
  </channel>
</rss>

