<?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 ContactPointEmail records orphaned after Person Account merge in DemandTools</title>
    <link>https://mycommunity.validity.com/t5/demandtools/contactpointemail-records-orphaned-after-person-account-merge/m-p/3024#M1726</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;We're using DemandTools to merge duplicate Person Accounts in our&amp;nbsp;org. We have ContactPointEmail&lt;BR /&gt;records associated with Person Accounts via the ParentId&lt;BR /&gt;Master-Detail field (polymorphic: Individual/Account). ( We adapt CPEs right before our dedupe project to not loose any email data in looser records.)&lt;/P&gt;&lt;P&gt;After merging duplicate Person Accounts, the ContactPointEmail&lt;BR /&gt;records from the losing account become orphaned.&lt;/P&gt;&lt;P&gt;Notes:&lt;BR /&gt;- ContactPointEmail is selected under Child Object Selection in&lt;BR /&gt;Merge Options (Customize Merge is checked)&lt;BR /&gt;- Allow Reparenting is enabled on the ParentId field&lt;BR /&gt;- Other polymorphic child objects reparent successfully&lt;BR /&gt;- Manual UI update of ParentId works fine&lt;/P&gt;&lt;P&gt;Is this a known limitation with ContactPointEmail in DemandTools? Or more general advices?&lt;BR /&gt;Is there a workaround or recommended two-step process for handling&lt;BR /&gt;CPE records post-merge?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Fri, 27 Mar 2026 21:41:42 GMT</pubDate>
    <dc:creator>doruksonmez</dc:creator>
    <dc:date>2026-03-27T21:41:42Z</dc:date>
    <item>
      <title>ContactPointEmail records orphaned after Person Account merge</title>
      <link>https://mycommunity.validity.com/t5/demandtools/contactpointemail-records-orphaned-after-person-account-merge/m-p/3024#M1726</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;We're using DemandTools to merge duplicate Person Accounts in our&amp;nbsp;org. We have ContactPointEmail&lt;BR /&gt;records associated with Person Accounts via the ParentId&lt;BR /&gt;Master-Detail field (polymorphic: Individual/Account). ( We adapt CPEs right before our dedupe project to not loose any email data in looser records.)&lt;/P&gt;&lt;P&gt;After merging duplicate Person Accounts, the ContactPointEmail&lt;BR /&gt;records from the losing account become orphaned.&lt;/P&gt;&lt;P&gt;Notes:&lt;BR /&gt;- ContactPointEmail is selected under Child Object Selection in&lt;BR /&gt;Merge Options (Customize Merge is checked)&lt;BR /&gt;- Allow Reparenting is enabled on the ParentId field&lt;BR /&gt;- Other polymorphic child objects reparent successfully&lt;BR /&gt;- Manual UI update of ParentId works fine&lt;/P&gt;&lt;P&gt;Is this a known limitation with ContactPointEmail in DemandTools? Or more general advices?&lt;BR /&gt;Is there a workaround or recommended two-step process for handling&lt;BR /&gt;CPE records post-merge?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Fri, 27 Mar 2026 21:41:42 GMT</pubDate>
      <guid>https://mycommunity.validity.com/t5/demandtools/contactpointemail-records-orphaned-after-person-account-merge/m-p/3024#M1726</guid>
      <dc:creator>doruksonmez</dc:creator>
      <dc:date>2026-03-27T21:41:42Z</dc:date>
    </item>
    <item>
      <title>Re: ContactPointEmail records orphaned after Person Account merge</title>
      <link>https://mycommunity.validity.com/t5/demandtools/contactpointemail-records-orphaned-after-person-account-merge/m-p/3025#M1727</link>
      <description>&lt;P&gt;Hey&amp;nbsp;&lt;a href="https://mycommunity.validity.com/t5/user/viewprofilepage/user-id/2786"&gt;@doruksonmez&lt;/a&gt;&amp;nbsp;- Great question. These unique setups need a more customized solution so we typically will handle them by first identifying duplicates, reparenting the child object, then processing the parent merge. I'll shoot you an email with more details on the step by step process!&lt;/P&gt;</description>
      <pubDate>Mon, 30 Mar 2026 21:42:36 GMT</pubDate>
      <guid>https://mycommunity.validity.com/t5/demandtools/contactpointemail-records-orphaned-after-person-account-merge/m-p/3025#M1727</guid>
      <dc:creator>Pugs_Validity</dc:creator>
      <dc:date>2026-03-30T21:42:36Z</dc:date>
    </item>
    <item>
      <title>Re: ContactPointEmail records orphaned after Person Account merge</title>
      <link>https://mycommunity.validity.com/t5/demandtools/contactpointemail-records-orphaned-after-person-account-merge/m-p/3026#M1728</link>
      <description>&lt;P class=""&gt;&lt;SPAN&gt;Thanks for the response!&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;That approach makes sense, but in our case (Industry Cloud with Person Accounts) we’re actually seeing a growing number of orphaned child records after merges during tests especially with contact related objects.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;It looks like the standard merge behavior isn’t consistently reparenting all child records in these scenarios. Have you seen similar issues specifically with Person Account merges in industry clouds, or is there a recommended way to ensure all related records are reliably reparented before/after the merge?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Appreciate any additional guidance you can share.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 31 Mar 2026 16:00:01 GMT</pubDate>
      <guid>https://mycommunity.validity.com/t5/demandtools/contactpointemail-records-orphaned-after-person-account-merge/m-p/3026#M1728</guid>
      <dc:creator>doruksonmez</dc:creator>
      <dc:date>2026-03-31T16:00:01Z</dc:date>
    </item>
    <item>
      <title>Re: ContactPointEmail records orphaned after Person Account merge</title>
      <link>https://mycommunity.validity.com/t5/demandtools/contactpointemail-records-orphaned-after-person-account-merge/m-p/3027#M1729</link>
      <description>&lt;P data-unlink="true"&gt;&lt;a href="https://mycommunity.validity.com/t5/user/viewprofilepage/user-id/2786"&gt;@doruksonmez&lt;/a&gt;&amp;nbsp;- You are seeing it with other related objects as well? I see you have a ticket and call scheduled with our support team. I'll be sure to collaborate with them if they are unable to provide a resolution on the call. Our general guidance for Person Accounts setups with DemandTools can be found &lt;A href="https://knowledge.validity.com/s/articles/DemandTools-V-and-Person-Accounts?language=en_US" target="_self"&gt;here&lt;/A&gt;.&amp;nbsp;There's a couple work arounds we can try out depending on your specific setup, I'm sure we'll find one that works best for you.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 31 Mar 2026 21:49:50 GMT</pubDate>
      <guid>https://mycommunity.validity.com/t5/demandtools/contactpointemail-records-orphaned-after-person-account-merge/m-p/3027#M1729</guid>
      <dc:creator>Pugs_Validity</dc:creator>
      <dc:date>2026-03-31T21:49:50Z</dc:date>
    </item>
  </channel>
</rss>

