<?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: Tune for Merges - Field Values Not Copied from Losing to Winning in DemandTools</title>
    <link>https://mycommunity.validity.com/t5/demandtools/tune-for-merges-field-values-not-copied-from-losing-to-winning/m-p/2338#M1259</link>
    <description>&lt;P&gt;Hey &lt;a href="https://mycommunity.validity.com/t5/user/viewprofilepage/user-id/928"&gt;@jazmindensmore&lt;/a&gt;&amp;nbsp;- I was unable to replicate this on my end as it appears to be following the proper "Update If Empty" logic from what I see in my testing. I noticed you are currently engaged on a ticket with my colleague, Amadou, on the support team. I'll ask him to add me on the call you all schedule together to review the use case.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 25 Oct 2024 13:59:07 GMT</pubDate>
    <dc:creator>Pugs_Validity</dc:creator>
    <dc:date>2024-10-25T13:59:07Z</dc:date>
    <item>
      <title>Tune for Merges - Field Values Not Copied from Losing to Winning</title>
      <link>https://mycommunity.validity.com/t5/demandtools/tune-for-merges-field-values-not-copied-from-losing-to-winning/m-p/2329#M1254</link>
      <description>&lt;P&gt;I have been using Tune in DemandTools V for single account merges, filtering to specific account IDs and merging one group at a time. I found today that when a field is populated on the losing record and empty on the winning, the value is not moving from the losing record to the winning record. I am losing valuable data when merging using Tune, and Dedupe is not a great module for my use case where I have two account IDs and have already determined they are duplicates.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a setting that needs to be adjusted to ensure a value is always moved from losing to winning if the winning has an empty value? Or is this a bug?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 22 Oct 2024 17:52:24 GMT</pubDate>
      <guid>https://mycommunity.validity.com/t5/demandtools/tune-for-merges-field-values-not-copied-from-losing-to-winning/m-p/2329#M1254</guid>
      <dc:creator>jazmindensmore</dc:creator>
      <dc:date>2024-10-22T17:52:24Z</dc:date>
    </item>
    <item>
      <title>Re: Tune for Merges - Field Values Not Copied from Losing to Winning</title>
      <link>https://mycommunity.validity.com/t5/demandtools/tune-for-merges-field-values-not-copied-from-losing-to-winning/m-p/2338#M1259</link>
      <description>&lt;P&gt;Hey &lt;a href="https://mycommunity.validity.com/t5/user/viewprofilepage/user-id/928"&gt;@jazmindensmore&lt;/a&gt;&amp;nbsp;- I was unable to replicate this on my end as it appears to be following the proper "Update If Empty" logic from what I see in my testing. I noticed you are currently engaged on a ticket with my colleague, Amadou, on the support team. I'll ask him to add me on the call you all schedule together to review the use case.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 25 Oct 2024 13:59:07 GMT</pubDate>
      <guid>https://mycommunity.validity.com/t5/demandtools/tune-for-merges-field-values-not-copied-from-losing-to-winning/m-p/2338#M1259</guid>
      <dc:creator>Pugs_Validity</dc:creator>
      <dc:date>2024-10-25T13:59:07Z</dc:date>
    </item>
  </channel>
</rss>

