<?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 Combining field values from multiple non-winning records in DemandTools</title>
    <link>https://mycommunity.validity.com/t5/demandtools/combining-field-values-from-multiple-non-winning-records/m-p/2902#M1646</link>
    <description>&lt;P&gt;A common concern we hear with Deduping records is the ability to retain valuable information from the same field across multiple records when merging.&lt;/P&gt;
&lt;P&gt;The initial solution for this within DemandTools was the &lt;A href="https://knowledge.validity.com/s/articles/Field-Rules?language=en_US" target="_blank"&gt;Field Copy Unique Field Rule&lt;/A&gt; in Dedupe. &lt;STRONG&gt;Field Copy Unique allows you to take a field from a non-winning record and populate it to an alternate field on the winning Record.&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Pugs_Validity_0-1759862672380.png" style="width: 999px;"&gt;&lt;img src="https://mycommunity.validity.com/t5/image/serverpage/image-id/784iFC8D5B4A39DDEBDF/image-size/large?v=v2&amp;amp;px=999" role="button" title="Pugs_Validity_0-1759862672380.png" alt="Pugs_Validity_0-1759862672380.png" /&gt;&lt;/span&gt;This approach can create a problem if you have multiple non-winning records and multiple unique values. &lt;STRONG&gt;Salesforce will only allow you to combine multiple values on a Multipicklist, Boolean, String, and Text Area field types.&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;This is where the &lt;STRONG&gt;Combine Field Value&lt;/STRONG&gt; steps in. If you use the field copy unique approach to copy the non-winning values to a combinable field type, you will then be given the option to &lt;STRONG&gt;check the combine field value checkbox&lt;/STRONG&gt; and combine multiple losing record’s value to the winning record.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Pugs_Validity_1-1759862672384.png" style="width: 999px;"&gt;&lt;img src="https://mycommunity.validity.com/t5/image/serverpage/image-id/785iD228F5D02A11AF5D/image-size/large?v=v2&amp;amp;px=999" role="button" title="Pugs_Validity_1-1759862672384.png" alt="Pugs_Validity_1-1759862672384.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;FieldCopyUnique:&lt;/STRONG&gt;&amp;nbsp;Update the field with a unique value from a selected field&lt;/P&gt;
&lt;UL&gt;
&lt;UL&gt;
&lt;LI&gt;Designed to auto-populate "alternate" fields. e.g. alternate email or alternate phone fields&lt;/LI&gt;
&lt;LI&gt;Can only select like field types to copy from, e.g. text field to text field, number field to number field etc.&lt;/LI&gt;
&lt;LI&gt;ONLY populates the selected field on the winning record with unique values&lt;/LI&gt;
&lt;LI&gt;The check for uniqueness is done by comparing data in the from field for all duplicate records in the group to the value in the from field on the winning record&lt;/LI&gt;
&lt;LI&gt;Unique values are then written to the target field&lt;/LI&gt;
&lt;LI&gt;If there are multiple unique values in the duplicate records, DemandTools will arbitrarily pick which one to keep&lt;/LI&gt;
&lt;UL&gt;
&lt;LI&gt;To specify which value to keep when there are multiples, use the FieldCopyUnique Scoring option instead&lt;/LI&gt;
&lt;/UL&gt;
&lt;LI&gt;If a value currently exists in the target field, it will ONLY update this field if the Overwrite checkbox on the right is selected&lt;/LI&gt;
&lt;LI&gt;Selecting the FieldCopyUnique option will highlight the Value box in yellow&lt;/LI&gt;
&lt;LI&gt;Click in the yellow highlight and select the field to copy unique data from&lt;/LI&gt;
&lt;LI&gt;The selected field will now be shown in the grid&lt;/LI&gt;
&lt;/UL&gt;
&lt;/UL&gt;</description>
    <pubDate>Tue, 07 Oct 2025 18:47:02 GMT</pubDate>
    <dc:creator>Pugs_Validity</dc:creator>
    <dc:date>2025-10-07T18:47:02Z</dc:date>
    <item>
      <title>Combining field values from multiple non-winning records</title>
      <link>https://mycommunity.validity.com/t5/demandtools/combining-field-values-from-multiple-non-winning-records/m-p/2902#M1646</link>
      <description>&lt;P&gt;A common concern we hear with Deduping records is the ability to retain valuable information from the same field across multiple records when merging.&lt;/P&gt;
&lt;P&gt;The initial solution for this within DemandTools was the &lt;A href="https://knowledge.validity.com/s/articles/Field-Rules?language=en_US" target="_blank"&gt;Field Copy Unique Field Rule&lt;/A&gt; in Dedupe. &lt;STRONG&gt;Field Copy Unique allows you to take a field from a non-winning record and populate it to an alternate field on the winning Record.&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Pugs_Validity_0-1759862672380.png" style="width: 999px;"&gt;&lt;img src="https://mycommunity.validity.com/t5/image/serverpage/image-id/784iFC8D5B4A39DDEBDF/image-size/large?v=v2&amp;amp;px=999" role="button" title="Pugs_Validity_0-1759862672380.png" alt="Pugs_Validity_0-1759862672380.png" /&gt;&lt;/span&gt;This approach can create a problem if you have multiple non-winning records and multiple unique values. &lt;STRONG&gt;Salesforce will only allow you to combine multiple values on a Multipicklist, Boolean, String, and Text Area field types.&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;This is where the &lt;STRONG&gt;Combine Field Value&lt;/STRONG&gt; steps in. If you use the field copy unique approach to copy the non-winning values to a combinable field type, you will then be given the option to &lt;STRONG&gt;check the combine field value checkbox&lt;/STRONG&gt; and combine multiple losing record’s value to the winning record.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Pugs_Validity_1-1759862672384.png" style="width: 999px;"&gt;&lt;img src="https://mycommunity.validity.com/t5/image/serverpage/image-id/785iD228F5D02A11AF5D/image-size/large?v=v2&amp;amp;px=999" role="button" title="Pugs_Validity_1-1759862672384.png" alt="Pugs_Validity_1-1759862672384.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;FieldCopyUnique:&lt;/STRONG&gt;&amp;nbsp;Update the field with a unique value from a selected field&lt;/P&gt;
&lt;UL&gt;
&lt;UL&gt;
&lt;LI&gt;Designed to auto-populate "alternate" fields. e.g. alternate email or alternate phone fields&lt;/LI&gt;
&lt;LI&gt;Can only select like field types to copy from, e.g. text field to text field, number field to number field etc.&lt;/LI&gt;
&lt;LI&gt;ONLY populates the selected field on the winning record with unique values&lt;/LI&gt;
&lt;LI&gt;The check for uniqueness is done by comparing data in the from field for all duplicate records in the group to the value in the from field on the winning record&lt;/LI&gt;
&lt;LI&gt;Unique values are then written to the target field&lt;/LI&gt;
&lt;LI&gt;If there are multiple unique values in the duplicate records, DemandTools will arbitrarily pick which one to keep&lt;/LI&gt;
&lt;UL&gt;
&lt;LI&gt;To specify which value to keep when there are multiples, use the FieldCopyUnique Scoring option instead&lt;/LI&gt;
&lt;/UL&gt;
&lt;LI&gt;If a value currently exists in the target field, it will ONLY update this field if the Overwrite checkbox on the right is selected&lt;/LI&gt;
&lt;LI&gt;Selecting the FieldCopyUnique option will highlight the Value box in yellow&lt;/LI&gt;
&lt;LI&gt;Click in the yellow highlight and select the field to copy unique data from&lt;/LI&gt;
&lt;LI&gt;The selected field will now be shown in the grid&lt;/LI&gt;
&lt;/UL&gt;
&lt;/UL&gt;</description>
      <pubDate>Tue, 07 Oct 2025 18:47:02 GMT</pubDate>
      <guid>https://mycommunity.validity.com/t5/demandtools/combining-field-values-from-multiple-non-winning-records/m-p/2902#M1646</guid>
      <dc:creator>Pugs_Validity</dc:creator>
      <dc:date>2025-10-07T18:47:02Z</dc:date>
    </item>
  </channel>
</rss>

