<?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 Using child objects for field rules in DemandTools</title>
    <link>https://mycommunity.validity.com/t5/demandtools/using-child-objects-for-field-rules/m-p/1352#M741</link>
    <description>&lt;P&gt;Is there a way to use child objects for scoring in field rules.&lt;BR /&gt;&lt;BR /&gt;I have a use case where I want to use a custom marketing data object, which contains information about how people interact with e-mails, to determine which e-mail should win when merging accounts.&lt;BR /&gt;&lt;BR /&gt;But I'm unsure how to do this without basically having to duplicate fields across multiple objects. If anyone can point me in the right direction, I would really appreciate it. Maybe I'm thinking about it all wrong.&lt;/P&gt;</description>
    <pubDate>Tue, 10 Oct 2023 14:51:01 GMT</pubDate>
    <dc:creator>artichokelight</dc:creator>
    <dc:date>2023-10-10T14:51:01Z</dc:date>
    <item>
      <title>Using child objects for field rules</title>
      <link>https://mycommunity.validity.com/t5/demandtools/using-child-objects-for-field-rules/m-p/1352#M741</link>
      <description>&lt;P&gt;Is there a way to use child objects for scoring in field rules.&lt;BR /&gt;&lt;BR /&gt;I have a use case where I want to use a custom marketing data object, which contains information about how people interact with e-mails, to determine which e-mail should win when merging accounts.&lt;BR /&gt;&lt;BR /&gt;But I'm unsure how to do this without basically having to duplicate fields across multiple objects. If anyone can point me in the right direction, I would really appreciate it. Maybe I'm thinking about it all wrong.&lt;/P&gt;</description>
      <pubDate>Tue, 10 Oct 2023 14:51:01 GMT</pubDate>
      <guid>https://mycommunity.validity.com/t5/demandtools/using-child-objects-for-field-rules/m-p/1352#M741</guid>
      <dc:creator>artichokelight</dc:creator>
      <dc:date>2023-10-10T14:51:01Z</dc:date>
    </item>
    <item>
      <title>Re: Using child objects for field rules</title>
      <link>https://mycommunity.validity.com/t5/demandtools/using-child-objects-for-field-rules/m-p/1356#M745</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://mycommunity.validity.com/t5/user/viewprofilepage/user-id/764"&gt;@artichokelight&lt;/a&gt;,&amp;nbsp;at this time Field Rules only allow users to score based on field level data from the object you're currently deduplicating. As you mentioned, one workaround would be to create a field on that object to hold that data, which can even be hidden from view of end users. I know this is not ideal, but it would allow you to achieve the mentioned use case.&lt;/P&gt;
&lt;P&gt;If you haven't already, I would highly suggest submitting this as a feature request within &lt;A href="https://my.validity.com/demandtools/products" target="_self"&gt;MyValidity&lt;/A&gt;. These feature requests are reviewed regularly by our product team &amp;amp; evaluated as potential features for future DemandTools releases. More information on submitting a feature request can be found &lt;A href="https://knowledge.validity.com/hc/en-us/articles/7989470176155-Requesting-a-Feature-in-DemandTools-V" target="_self"&gt;here&lt;/A&gt;. Thank you!!&lt;/P&gt;</description>
      <pubDate>Wed, 11 Oct 2023 12:25:24 GMT</pubDate>
      <guid>https://mycommunity.validity.com/t5/demandtools/using-child-objects-for-field-rules/m-p/1356#M745</guid>
      <dc:creator>JonG_Validity</dc:creator>
      <dc:date>2023-10-11T12:25:24Z</dc:date>
    </item>
  </channel>
</rss>

