<?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 Salesforce EDA Package - Deduping Contacts - What's the best way to reparent relationships? in DemandTools</title>
    <link>https://mycommunity.validity.com/t5/demandtools/salesforce-eda-package-deduping-contacts-what-s-the-best-way-to/m-p/1512#M823</link>
    <description>&lt;P&gt;In EDA in Salesforce, there are relationship records that connect a Contact with a Related Contact. So a relationship could link a parent to a child, for example, with the type "Parent.' There is validation logic set up that prevents you from changing the Contact or Related Contact on a relationship record, saying "Instead of changing the Contacts in this Relationship, either delete this record, or if appropriate, add an end date and update the status to Former. Then create a new Relationship record between the new Contacts." This is default EDA functionality. I'm wondering what the recommended action is&amp;nbsp; when deduping. When I go to merge two records and the loser has a relationship, I want it to be reparented, but the validation logic above stops me. Has anyone else run into this, or does anyone have suggestions on what to do?&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 28 Nov 2023 02:04:30 GMT</pubDate>
    <dc:creator>lydiam8</dc:creator>
    <dc:date>2023-11-28T02:04:30Z</dc:date>
    <item>
      <title>Salesforce EDA Package - Deduping Contacts - What's the best way to reparent relationships?</title>
      <link>https://mycommunity.validity.com/t5/demandtools/salesforce-eda-package-deduping-contacts-what-s-the-best-way-to/m-p/1512#M823</link>
      <description>&lt;P&gt;In EDA in Salesforce, there are relationship records that connect a Contact with a Related Contact. So a relationship could link a parent to a child, for example, with the type "Parent.' There is validation logic set up that prevents you from changing the Contact or Related Contact on a relationship record, saying "Instead of changing the Contacts in this Relationship, either delete this record, or if appropriate, add an end date and update the status to Former. Then create a new Relationship record between the new Contacts." This is default EDA functionality. I'm wondering what the recommended action is&amp;nbsp; when deduping. When I go to merge two records and the loser has a relationship, I want it to be reparented, but the validation logic above stops me. Has anyone else run into this, or does anyone have suggestions on what to do?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Nov 2023 02:04:30 GMT</pubDate>
      <guid>https://mycommunity.validity.com/t5/demandtools/salesforce-eda-package-deduping-contacts-what-s-the-best-way-to/m-p/1512#M823</guid>
      <dc:creator>lydiam8</dc:creator>
      <dc:date>2023-11-28T02:04:30Z</dc:date>
    </item>
    <item>
      <title>Re: Salesforce EDA Package - Deduping Contacts - What's the best way to reparent relationships?</title>
      <link>https://mycommunity.validity.com/t5/demandtools/salesforce-eda-package-deduping-contacts-what-s-the-best-way-to/m-p/1514#M825</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://mycommunity.validity.com/t5/user/viewprofilepage/user-id/1062"&gt;@lydiam8&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;I'm going to reach out to you about this privately.&amp;nbsp; This will most likely require a multistep process.&lt;/P&gt;
&lt;P&gt;Regards,&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Nov 2023 12:45:54 GMT</pubDate>
      <guid>https://mycommunity.validity.com/t5/demandtools/salesforce-eda-package-deduping-contacts-what-s-the-best-way-to/m-p/1514#M825</guid>
      <dc:creator>AnthonyValidity</dc:creator>
      <dc:date>2023-11-28T12:45:54Z</dc:date>
    </item>
  </channel>
</rss>

