<?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 Clarification on working with related tables in existing feature services in ArcGIS Survey123 Questions</title>
    <link>https://community.esri.com/t5/arcgis-survey123-questions/clarification-on-working-with-related-tables-in/m-p/819066#M15321</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Based on the info I've found, when building surveys from existing feature services using relationships, the GlobalID must be used for the relationship. I want to make sure I'm setting up my feature services properly, can you confirm&amp;nbsp;&lt;A href="https://community.esri.com/migrated-users/3263"&gt;James Tedrick&lt;/A&gt;‌&amp;nbsp;&amp;nbsp;(see attachment)?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are there any other caveats or best practices to follow?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 25 Jul 2018 13:50:39 GMT</pubDate>
    <dc:creator>RobertBlash_HMM</dc:creator>
    <dc:date>2018-07-25T13:50:39Z</dc:date>
    <item>
      <title>Clarification on working with related tables in existing feature services</title>
      <link>https://community.esri.com/t5/arcgis-survey123-questions/clarification-on-working-with-related-tables-in/m-p/819066#M15321</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Based on the info I've found, when building surveys from existing feature services using relationships, the GlobalID must be used for the relationship. I want to make sure I'm setting up my feature services properly, can you confirm&amp;nbsp;&lt;A href="https://community.esri.com/migrated-users/3263"&gt;James Tedrick&lt;/A&gt;‌&amp;nbsp;&amp;nbsp;(see attachment)?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are there any other caveats or best practices to follow?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Jul 2018 13:50:39 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-survey123-questions/clarification-on-working-with-related-tables-in/m-p/819066#M15321</guid>
      <dc:creator>RobertBlash_HMM</dc:creator>
      <dc:date>2018-07-25T13:50:39Z</dc:date>
    </item>
    <item>
      <title>Re: Clarification on working with related tables in existing feature services</title>
      <link>https://community.esri.com/t5/arcgis-survey123-questions/clarification-on-working-with-related-tables-in/m-p/819067#M15322</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Robert&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is correct. Please see the following for full feature service requirements:&amp;nbsp;&lt;A class="link-titled" href="http://doc.arcgis.com/en/survey123/desktop/create-surveys/survey123withexistingfeatureservices.htm" title="http://doc.arcgis.com/en/survey123/desktop/create-surveys/survey123withexistingfeatureservices.htm"&gt;Use Survey123 with existing feature services—Survey123 for ArcGIS | ArcGIS&lt;/A&gt;&amp;nbsp;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you publish the service, enable sync - this is a good test to make sure the feature service is correctly configured.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;John&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Jul 2018 01:21:46 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-survey123-questions/clarification-on-working-with-related-tables-in/m-p/819067#M15322</guid>
      <dc:creator>JohnathanHasthorpe</dc:creator>
      <dc:date>2018-07-26T01:21:46Z</dc:date>
    </item>
  </channel>
</rss>

