<?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>idea Duplicate Record Split policy for GUID To GUID Relationships in ArcGIS Pro Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pro-ideas/duplicate-record-split-policy-for-guid-to-guid/idi-p/1570655</link>
    <description>&lt;P&gt;Allow users to set the split policy of related records to 'duplicate related objects' when the relationship is based on GUID to GUID fields.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Currently ArcPro only allows the split policy to be set to&amp;nbsp;'duplicate related objects' if the relationship is based on a GlobalID parent key field and a GUID foreign key field. However Esri Sweet and other non-Esri database systems require a GUID&amp;nbsp;parent key field and a GUID foreign key field to work, so the duplicate split policy can't be set for these relationships.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Not being able to set the split policy to&amp;nbsp;'duplicate related objects' leads to loss of related records from all but the largest feature when it is split.&lt;/P&gt;</description>
    <pubDate>Fri, 20 Dec 2024 16:45:07 GMT</pubDate>
    <dc:creator>amitchinson</dc:creator>
    <dc:date>2024-12-20T16:45:07Z</dc:date>
    <item>
      <title>Duplicate Record Split policy for GUID To GUID Relationships</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/duplicate-record-split-policy-for-guid-to-guid/idi-p/1570655</link>
      <description>&lt;P&gt;Allow users to set the split policy of related records to 'duplicate related objects' when the relationship is based on GUID to GUID fields.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Currently ArcPro only allows the split policy to be set to&amp;nbsp;'duplicate related objects' if the relationship is based on a GlobalID parent key field and a GUID foreign key field. However Esri Sweet and other non-Esri database systems require a GUID&amp;nbsp;parent key field and a GUID foreign key field to work, so the duplicate split policy can't be set for these relationships.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Not being able to set the split policy to&amp;nbsp;'duplicate related objects' leads to loss of related records from all but the largest feature when it is split.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Dec 2024 16:45:07 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/duplicate-record-split-policy-for-guid-to-guid/idi-p/1570655</guid>
      <dc:creator>amitchinson</dc:creator>
      <dc:date>2024-12-20T16:45:07Z</dc:date>
    </item>
    <item>
      <title>Re: Duplicate Record Split policy for GUID To GUID Relationships</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/duplicate-record-split-policy-for-guid-to-guid/idc-p/1583485#M33732</link>
      <description>&lt;P&gt;We need this too - please.&lt;BR /&gt;We are sometimes splitting 20 or so records at a time and it is very time consuming an error prone to go back and re-establish the relationships to multiple tables&lt;/P&gt;</description>
      <pubDate>Mon, 10 Feb 2025 01:21:32 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/duplicate-record-split-policy-for-guid-to-guid/idc-p/1583485#M33732</guid>
      <dc:creator>cpmgisuser</dc:creator>
      <dc:date>2025-02-10T01:21:32Z</dc:date>
    </item>
  </channel>
</rss>

