<?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: Survey123 3.9 Issues - Start Date/ select_one's in ArcGIS Survey123 Questions</title>
    <link>https://community.esri.com/t5/arcgis-survey123-questions/survey123-3-9-issues-start-date-select-one-s/m-p/784014#M6795</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi James - I have another update - it sounds like users are copying the previous survey data into a new survey and this is how it is happening. There are two cases that we commonly see with regards to the startdate/enddate field types:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Start date is populated but has the date from the previous copied survey&lt;/P&gt;&lt;P&gt;2. Start date is not populated - I think this is because the start date field was added to the survey and then republished - so earlier surveys didn't have that data field. So when the user copies the survey to a new one - it brings over the empty startdate field.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think the solution here would be to re-populate start and end field types when survey data is copied to new survey. Let me know if this doesn't make sense.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 27 May 2020 14:41:06 GMT</pubDate>
    <dc:creator>roemhildtg</dc:creator>
    <dc:date>2020-05-27T14:41:06Z</dc:date>
    <item>
      <title>Survey123 3.9 Issues - Start Date/ select_one's</title>
      <link>https://community.esri.com/t5/arcgis-survey123-questions/survey123-3-9-issues-start-date-select-one-s/m-p/784012#M6793</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just wondering if anyone has ran into the issues we're seeing. Beginning on April 4, 2020 - we started experiencing these issues. It seems to coincide with the 3.9 release (which was a couple of days before).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The issues I'm referencing appear to happen sporadically on IOS/iPad devices.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 22px;"&gt;Issue #1 - Start date/times no longer populate&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 15px;"&gt;In the screenshot below, start dates with the field type "start" are no longer populating for some users. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 22px;"&gt;&lt;IMG class="image-1 jive-image" src="https://community.esri.com/legacyfs/online/488838_pastedImage_1.png" /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 22px;"&gt;&lt;IMG class="image-2 jive-image" src="https://community.esri.com/legacyfs/online/488839_pastedImage_2.png" /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 30px;"&gt;Issue #2 Domain (select_one) not populating:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 15px;"&gt;In this screenshot - PipeXcelCO is the value that should be populated, but for some reason "pipeline Xcel Colorado" is getting populated somewhere.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 30px;"&gt;&lt;IMG class="image-3 jive-image" src="https://community.esri.com/legacyfs/online/488856_pastedImage_6.png" /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 15px;"&gt;List options page:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 30px;"&gt;&lt;IMG class="jive-image image-4" src="https://community.esri.com/legacyfs/online/488857_pastedImage_7.png" /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 15px;"&gt;This one I'm not so sure is an issue with survey123. It smells like user error but I thought I would throw it in here just to see if anyone has seen it before. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Apr 2020 13:06:40 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-survey123-questions/survey123-3-9-issues-start-date-select-one-s/m-p/784012#M6793</guid>
      <dc:creator>roemhildtg</dc:creator>
      <dc:date>2020-04-16T13:06:40Z</dc:date>
    </item>
    <item>
      <title>Re: Survey123 3.9 Issues - Start Date/ select_one's</title>
      <link>https://community.esri.com/t5/arcgis-survey123-questions/survey123-3-9-issues-start-date-select-one-s/m-p/784013#M6794</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Gregg,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Apologies for the delay in responding. &amp;nbsp;I tested a start field named startdate and it is writing values as expected. &amp;nbsp;If this continues, you may want to file a support ticket with the user you are seeing this occur for.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 May 2020 18:14:53 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-survey123-questions/survey123-3-9-issues-start-date-select-one-s/m-p/784013#M6794</guid>
      <dc:creator>JamesTedrick</dc:creator>
      <dc:date>2020-05-04T18:14:53Z</dc:date>
    </item>
    <item>
      <title>Re: Survey123 3.9 Issues - Start Date/ select_one's</title>
      <link>https://community.esri.com/t5/arcgis-survey123-questions/survey123-3-9-issues-start-date-select-one-s/m-p/784014#M6795</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi James - I have another update - it sounds like users are copying the previous survey data into a new survey and this is how it is happening. There are two cases that we commonly see with regards to the startdate/enddate field types:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Start date is populated but has the date from the previous copied survey&lt;/P&gt;&lt;P&gt;2. Start date is not populated - I think this is because the start date field was added to the survey and then republished - so earlier surveys didn't have that data field. So when the user copies the survey to a new one - it brings over the empty startdate field.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think the solution here would be to re-populate start and end field types when survey data is copied to new survey. Let me know if this doesn't make sense.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 May 2020 14:41:06 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-survey123-questions/survey123-3-9-issues-start-date-select-one-s/m-p/784014#M6795</guid>
      <dc:creator>roemhildtg</dc:creator>
      <dc:date>2020-05-27T14:41:06Z</dc:date>
    </item>
    <item>
      <title>Re: Survey123 3.9 Issues - Start Date/ select_one's</title>
      <link>https://community.esri.com/t5/arcgis-survey123-questions/survey123-3-9-issues-start-date-select-one-s/m-p/784015#M6796</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A href="https://community.esri.com/migrated-users/3263"&gt;James Tedrick&lt;/A&gt;‌ have you seen my previous message? We were just wondering because users keep running into the issue and I'm fairly certain this is pretty simple to reproduce. Just submit a survey, then from the sent folder, choose the option to copy the data into a new survey. It seems the calculated fields do not update and are instead copied over. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Jun 2020 16:01:42 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-survey123-questions/survey123-3-9-issues-start-date-select-one-s/m-p/784015#M6796</guid>
      <dc:creator>roemhildtg</dc:creator>
      <dc:date>2020-06-11T16:01:42Z</dc:date>
    </item>
    <item>
      <title>Re: Survey123 3.9 Issues - Start Date/ select_one's</title>
      <link>https://community.esri.com/t5/arcgis-survey123-questions/survey123-3-9-issues-start-date-select-one-s/m-p/784016#M6797</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Gregg,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My apologies, but I've not been able to be on GeoNet as much as I would like. &amp;nbsp;Yes, the start time is copied along with the other data when you choose to copy an existing record. &amp;nbsp;Survey123 Connect does not update domains when republishing a form; there is an enhancement request (ENH-000106608) to have it update the domain on republish.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Jun 2020 17:24:21 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-survey123-questions/survey123-3-9-issues-start-date-select-one-s/m-p/784016#M6797</guid>
      <dc:creator>JamesTedrick</dc:creator>
      <dc:date>2020-06-11T17:24:21Z</dc:date>
    </item>
    <item>
      <title>Re: Survey123 3.9 Issues - Start Date/ select_one's</title>
      <link>https://community.esri.com/t5/arcgis-survey123-questions/survey123-3-9-issues-start-date-select-one-s/m-p/1217740#M45088</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/192343"&gt;@roemhildtg&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;Just wanted to let you know with the upcoming 3.16 October Release of Survey123 we have made improvements to the Connect publishing workflow with regards to domains and choice lists. You can check out the latest announcement, documentation and test out the latest 3.16 beta builds via the &lt;A href="https://earlyadopter.esri.com/project/home.html?cap=%7Be69ef91f-4574-4b98-882c-651f7b518eb7%7D" target="_self"&gt;Early Adopter Community&lt;/A&gt; to get early access to these builds and the new Connect publishing workflows. You feedback on these improvements would be greatly appreciated.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Phil.&lt;/P&gt;</description>
      <pubDate>Fri, 30 Sep 2022 06:11:38 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-survey123-questions/survey123-3-9-issues-start-date-select-one-s/m-p/1217740#M45088</guid>
      <dc:creator>Anonymous User</dc:creator>
      <dc:date>2022-09-30T06:11:38Z</dc:date>
    </item>
  </channel>
</rss>

