<?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 Editing via Webform removes second location in ArcGIS Survey123 Questions</title>
    <link>https://community.esri.com/t5/arcgis-survey123-questions/editing-via-webform-removes-second-location/m-p/1318565#M51165</link>
    <description>&lt;P&gt;We have built a survey123 that is accessed and edited by users from within a dashboard.&amp;nbsp; The survey allows the user to record two locations: a geoshape that is stored as the records location and a point that is used to populate latitude and longitude reference fields used in geoenrichment.&amp;nbsp; It is important to note the point is not passed through with the record as the bind::esri:fieldType is null.&amp;nbsp; There are no conditions, repeats, calculations, relevants, etc... on either of these geometry fields as they are both required.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Users can create records without issue - the latitude and longitude reference points are populated as expected from a pulldata on the point geometry. The issue comes in, however, when users then go to edit the record from within the dashboard.&amp;nbsp; When a record is selected to be edited, almost all of the record's editable attributes populate - the geoshape question is populated as expected but the geopoint question appears blank, not carrying over the originally submitted point.&amp;nbsp; &amp;nbsp;&lt;/P&gt;&lt;P&gt;I've done a bit of troubleshooting, reviewing blogs and trying the suggestions but without success.&amp;nbsp; Any ideas on why the point is not coming back for editing?&amp;nbsp; Is it because of the null setting in the&amp;nbsp;bind::esri:fieldType?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Some troubleshooting step tried so far:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;I tried defaulting the point location to be the stored latitude and longitude (hoping I could force it back to the originally submitted point when a user goes in to edit) but that did not work - the point was still gone&lt;/LI&gt;&lt;LI&gt;I made a separate survey specifically for editing and pointed it at the original survey.&amp;nbsp; In the "editing" version, I removed the pulldata functions from the hidden latitude and longitude field, trying to avoind them getting reset when a record is edited.&amp;nbsp; While it looks like this would work, not having the pulldata functions means that if the customers do update that reference point to a different roadway, we won't be able to capture that information and geoenrich on the new location.&amp;nbsp; The record would be forever stuck having principal route information stored in the attributes which might not be accurate.&amp;nbsp;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;We typically try to avoid using repeats because they tend to get finicky - but this is the only other thing I can think of as potentially working. Is losing the second geometry while editing via a webform expected and I missed that somewhere? Or is it because of the null&amp;nbsp;bind::esri:fieldType?&lt;/P&gt;</description>
    <pubDate>Tue, 15 Aug 2023 03:25:17 GMT</pubDate>
    <dc:creator>KYTCGIS</dc:creator>
    <dc:date>2023-08-15T03:25:17Z</dc:date>
    <item>
      <title>Editing via Webform removes second location</title>
      <link>https://community.esri.com/t5/arcgis-survey123-questions/editing-via-webform-removes-second-location/m-p/1318565#M51165</link>
      <description>&lt;P&gt;We have built a survey123 that is accessed and edited by users from within a dashboard.&amp;nbsp; The survey allows the user to record two locations: a geoshape that is stored as the records location and a point that is used to populate latitude and longitude reference fields used in geoenrichment.&amp;nbsp; It is important to note the point is not passed through with the record as the bind::esri:fieldType is null.&amp;nbsp; There are no conditions, repeats, calculations, relevants, etc... on either of these geometry fields as they are both required.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Users can create records without issue - the latitude and longitude reference points are populated as expected from a pulldata on the point geometry. The issue comes in, however, when users then go to edit the record from within the dashboard.&amp;nbsp; When a record is selected to be edited, almost all of the record's editable attributes populate - the geoshape question is populated as expected but the geopoint question appears blank, not carrying over the originally submitted point.&amp;nbsp; &amp;nbsp;&lt;/P&gt;&lt;P&gt;I've done a bit of troubleshooting, reviewing blogs and trying the suggestions but without success.&amp;nbsp; Any ideas on why the point is not coming back for editing?&amp;nbsp; Is it because of the null setting in the&amp;nbsp;bind::esri:fieldType?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Some troubleshooting step tried so far:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;I tried defaulting the point location to be the stored latitude and longitude (hoping I could force it back to the originally submitted point when a user goes in to edit) but that did not work - the point was still gone&lt;/LI&gt;&lt;LI&gt;I made a separate survey specifically for editing and pointed it at the original survey.&amp;nbsp; In the "editing" version, I removed the pulldata functions from the hidden latitude and longitude field, trying to avoind them getting reset when a record is edited.&amp;nbsp; While it looks like this would work, not having the pulldata functions means that if the customers do update that reference point to a different roadway, we won't be able to capture that information and geoenrich on the new location.&amp;nbsp; The record would be forever stuck having principal route information stored in the attributes which might not be accurate.&amp;nbsp;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;We typically try to avoid using repeats because they tend to get finicky - but this is the only other thing I can think of as potentially working. Is losing the second geometry while editing via a webform expected and I missed that somewhere? Or is it because of the null&amp;nbsp;bind::esri:fieldType?&lt;/P&gt;</description>
      <pubDate>Tue, 15 Aug 2023 03:25:17 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-survey123-questions/editing-via-webform-removes-second-location/m-p/1318565#M51165</guid>
      <dc:creator>KYTCGIS</dc:creator>
      <dc:date>2023-08-15T03:25:17Z</dc:date>
    </item>
  </channel>
</rss>

