<?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 Issue with values in nested repeat being cleared when prior records are deleted in ArcGIS Survey123 Questions</title>
    <link>https://community.esri.com/t5/arcgis-survey123-questions/issue-with-values-in-nested-repeat-being-cleared/m-p/1111350#M38294</link>
    <description>&lt;P&gt;I am currently running into an issue with a survey where I have a nested repeat that is only relevant sometimes based on a question in its parent record. Everything works as expected except in the scenario where the nested repeat record is not relevant on the first repeat record but a nested repeat record is created for the second record. If I then delete the first repeat record all information for the nested repeat record associated with the second record is cleared.&amp;nbsp;&lt;/P&gt;&lt;P&gt;To use the Nested Repeats Sample from Survey123 Connect as an example:&lt;/P&gt;&lt;P&gt;If I create a field called equipment_in_campsite in the campsites repeat, set it to default to "no", and then make the campsite_equipment repeat relevant only if equipment_in_campsite = "yes" I see the following behavior.&lt;/P&gt;&lt;P&gt;If campsite 1 has no equipment associated with it and campsite 2 does and I delete the record for campsite 1, all information that I have entered for the equipment in campsite 2 is cleared.&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is obviously a highly artificial example but a field crew recently encountered this behavior in a form I designed and I wanted to bring it to your attention since it was definitely unexpected. I've attached a modification of the Nested repeats sample that demonstrates this behavior.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 26 Oct 2021 17:14:33 GMT</pubDate>
    <dc:creator>AndyMcClary</dc:creator>
    <dc:date>2021-10-26T17:14:33Z</dc:date>
    <item>
      <title>Issue with values in nested repeat being cleared when prior records are deleted</title>
      <link>https://community.esri.com/t5/arcgis-survey123-questions/issue-with-values-in-nested-repeat-being-cleared/m-p/1111350#M38294</link>
      <description>&lt;P&gt;I am currently running into an issue with a survey where I have a nested repeat that is only relevant sometimes based on a question in its parent record. Everything works as expected except in the scenario where the nested repeat record is not relevant on the first repeat record but a nested repeat record is created for the second record. If I then delete the first repeat record all information for the nested repeat record associated with the second record is cleared.&amp;nbsp;&lt;/P&gt;&lt;P&gt;To use the Nested Repeats Sample from Survey123 Connect as an example:&lt;/P&gt;&lt;P&gt;If I create a field called equipment_in_campsite in the campsites repeat, set it to default to "no", and then make the campsite_equipment repeat relevant only if equipment_in_campsite = "yes" I see the following behavior.&lt;/P&gt;&lt;P&gt;If campsite 1 has no equipment associated with it and campsite 2 does and I delete the record for campsite 1, all information that I have entered for the equipment in campsite 2 is cleared.&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is obviously a highly artificial example but a field crew recently encountered this behavior in a form I designed and I wanted to bring it to your attention since it was definitely unexpected. I've attached a modification of the Nested repeats sample that demonstrates this behavior.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 26 Oct 2021 17:14:33 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-survey123-questions/issue-with-values-in-nested-repeat-being-cleared/m-p/1111350#M38294</guid>
      <dc:creator>AndyMcClary</dc:creator>
      <dc:date>2021-10-26T17:14:33Z</dc:date>
    </item>
  </channel>
</rss>

