<?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: Advancing Occurrences of Communication Nodes in SAS Customer Intelligence</title>
    <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/Advancing-Occurrences-of-Communication-Nodes/m-p/296121#M216</link>
    <description>The occurrence number is tracked inside the campaign object; what's written to the CDM is just recording what it is at that time, so your approach should work fine, and is the only mechanism I know of. It might also be possible to use the integration utilities to export it to XML and find/update the occurrence number, then use the Update action to get it back into metadata, but that's a lot riskier, IMHO.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Fri, 02 Sep 2016 14:15:09 GMT</pubDate>
    <dc:creator>shill</dc:creator>
    <dc:date>2016-09-02T14:15:09Z</dc:date>
    <item>
      <title>Advancing Occurrences of Communication Nodes</title>
      <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/Advancing-Occurrences-of-Communication-Nodes/m-p/296113#M215</link>
      <description>&lt;P&gt;Is there a way to get a newly added communication node's occurence number up to a count that matches the other communication nodes? It needs to be connected to a cell in order to execute. I think the best way would be to disable the communication node from writing to contact history and executing the node the necessary amount of times to get it up to the correct count. Then re-enable writing to contact history.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Would that work? Does CIS track the occurrences outside of CDM so that when I re-enable writing to contact history it skips a number of occurences?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 02 Sep 2016 13:50:55 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Customer-Intelligence/Advancing-Occurrences-of-Communication-Nodes/m-p/296113#M215</guid>
      <dc:creator>pcapazzi</dc:creator>
      <dc:date>2016-09-02T13:50:55Z</dc:date>
    </item>
    <item>
      <title>Re: Advancing Occurrences of Communication Nodes</title>
      <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/Advancing-Occurrences-of-Communication-Nodes/m-p/296121#M216</link>
      <description>The occurrence number is tracked inside the campaign object; what's written to the CDM is just recording what it is at that time, so your approach should work fine, and is the only mechanism I know of. It might also be possible to use the integration utilities to export it to XML and find/update the occurrence number, then use the Update action to get it back into metadata, but that's a lot riskier, IMHO.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 02 Sep 2016 14:15:09 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Customer-Intelligence/Advancing-Occurrences-of-Communication-Nodes/m-p/296121#M216</guid>
      <dc:creator>shill</dc:creator>
      <dc:date>2016-09-02T14:15:09Z</dc:date>
    </item>
  </channel>
</rss>

