<?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 Duplicating Related Records in ArcCollector for Android in ArcGIS Collector Questions</title>
    <link>https://community.esri.com/t5/arcgis-collector-questions/duplicating-related-records-in-arccollector-for/m-p/428492#M7363</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Our enterprise geodatabase has two feature classes relating to a single table (1:M, simple, None messages, GlobalID to GUID). We published a single service from both feature classes and the related table. &amp;nbsp;For some reason, when we collect related records on feature class A, the globalID from feature class B is getting populated in the related table. &amp;nbsp;It seems to be 'grabbing' the related records from surrounding features from feature A. This is causing many issues. &amp;nbsp;In some cases, as many as 40 records relate back to a single point in feature class B which is not correct. &amp;nbsp;We noticed it only happens when running ArcCollector on Andriod OS.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;See the attached image. &amp;nbsp;I know this is a confusing question, but we need to get this squared away as soon as possible.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The images shows 24 table records relating to 1 point feature in feature class B, and 8 in feature class A. Our relationships are not set up to where a GUID would be populated for BOTH FC A guid and FC B guid. &amp;nbsp;It should be either one or the other.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 15 Nov 2016 19:37:03 GMT</pubDate>
    <dc:creator>MitchHolley1</dc:creator>
    <dc:date>2016-11-15T19:37:03Z</dc:date>
    <item>
      <title>Duplicating Related Records in ArcCollector for Android</title>
      <link>https://community.esri.com/t5/arcgis-collector-questions/duplicating-related-records-in-arccollector-for/m-p/428492#M7363</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Our enterprise geodatabase has two feature classes relating to a single table (1:M, simple, None messages, GlobalID to GUID). We published a single service from both feature classes and the related table. &amp;nbsp;For some reason, when we collect related records on feature class A, the globalID from feature class B is getting populated in the related table. &amp;nbsp;It seems to be 'grabbing' the related records from surrounding features from feature A. This is causing many issues. &amp;nbsp;In some cases, as many as 40 records relate back to a single point in feature class B which is not correct. &amp;nbsp;We noticed it only happens when running ArcCollector on Andriod OS.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;See the attached image. &amp;nbsp;I know this is a confusing question, but we need to get this squared away as soon as possible.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The images shows 24 table records relating to 1 point feature in feature class B, and 8 in feature class A. Our relationships are not set up to where a GUID would be populated for BOTH FC A guid and FC B guid. &amp;nbsp;It should be either one or the other.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Nov 2016 19:37:03 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-collector-questions/duplicating-related-records-in-arccollector-for/m-p/428492#M7363</guid>
      <dc:creator>MitchHolley1</dc:creator>
      <dc:date>2016-11-15T19:37:03Z</dc:date>
    </item>
  </channel>
</rss>

