<?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 Re: How to do a fake email field change in DemandTools</title>
    <link>https://mycommunity.validity.com/t5/demandtools/how-to-do-a-fake-email-field-change/m-p/1313#M719</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://mycommunity.validity.com/t5/user/viewprofilepage/user-id/276"&gt;@michael-wtds&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;Hope you're doing well!&amp;nbsp; If you're using Saleforce's native duplicate management and "&lt;SPAN&gt;the rule only runs on edited records when the edited fields are included in the associated matching rule" then I think your way is best.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;I do want to point out that DupeBlocker, which is included in your contract, doesn't require a specific field to be updated (just an update).&amp;nbsp; Also, it can also trigger a warning or "set" by just viewing the record.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 25 Sep 2023 13:54:38 GMT</pubDate>
    <dc:creator>AnthonyValidity</dc:creator>
    <dc:date>2023-09-25T13:54:38Z</dc:date>
    <item>
      <title>How to do a fake email field change</title>
      <link>https://mycommunity.validity.com/t5/demandtools/how-to-do-a-fake-email-field-change/m-p/1310#M717</link>
      <description>&lt;P&gt;I'm trying to force a Salesforce duplicate rule to fire for contacts with the same email address, so that I can create reports from the Duplicate Record Set data.&amp;nbsp; However, the only way to get the duplicate record set records created is to make a change to the existing email addresses.&lt;/P&gt;&lt;P&gt;It seems my only option is to export the known duplicate email address records to a file, with the record ID, and do a blank email update, and then repeat the update to put back the original email address.&amp;nbsp; However, I would like to avoid blanking out the email address for audit tracking.&lt;/P&gt;&lt;P&gt;Any other suggestions on how to make this update?&lt;/P&gt;&lt;P&gt;Thanks!&lt;BR /&gt;Michael&lt;/P&gt;</description>
      <pubDate>Thu, 21 Sep 2023 16:56:22 GMT</pubDate>
      <guid>https://mycommunity.validity.com/t5/demandtools/how-to-do-a-fake-email-field-change/m-p/1310#M717</guid>
      <dc:creator>michael-wtds</dc:creator>
      <dc:date>2023-09-21T16:56:22Z</dc:date>
    </item>
    <item>
      <title>Re: How to do a fake email field change</title>
      <link>https://mycommunity.validity.com/t5/demandtools/how-to-do-a-fake-email-field-change/m-p/1313#M719</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://mycommunity.validity.com/t5/user/viewprofilepage/user-id/276"&gt;@michael-wtds&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;Hope you're doing well!&amp;nbsp; If you're using Saleforce's native duplicate management and "&lt;SPAN&gt;the rule only runs on edited records when the edited fields are included in the associated matching rule" then I think your way is best.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;I do want to point out that DupeBlocker, which is included in your contract, doesn't require a specific field to be updated (just an update).&amp;nbsp; Also, it can also trigger a warning or "set" by just viewing the record.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 25 Sep 2023 13:54:38 GMT</pubDate>
      <guid>https://mycommunity.validity.com/t5/demandtools/how-to-do-a-fake-email-field-change/m-p/1313#M719</guid>
      <dc:creator>AnthonyValidity</dc:creator>
      <dc:date>2023-09-25T13:54:38Z</dc:date>
    </item>
  </channel>
</rss>

