<?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 How to set the sequence number campaign code &amp;amp; communication code? in SAS Customer Intelligence</title>
    <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/How-to-set-the-sequence-number-campaign-code-amp-communication/m-p/397984#M610</link>
    <description>&lt;P&gt;&lt;BR /&gt;The current campaign code structure is C##### (5 digits). The current used number is around 55000.&lt;BR /&gt;The client would like to continue the number in the new system. Therefore, e.g.: starting from 55001.&lt;BR /&gt;This also applies to the communication.Please also advise if any other sequence number need to be updated.&amp;nbsp;As I remember, there is a .sas file containing those numbers, which stored in the SAS application folder. please advise me&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 22 Sep 2017 04:50:41 GMT</pubDate>
    <dc:creator>Amarnadh</dc:creator>
    <dc:date>2017-09-22T04:50:41Z</dc:date>
    <item>
      <title>How to set the sequence number campaign code &amp; communication code?</title>
      <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/How-to-set-the-sequence-number-campaign-code-amp-communication/m-p/397984#M610</link>
      <description>&lt;P&gt;&lt;BR /&gt;The current campaign code structure is C##### (5 digits). The current used number is around 55000.&lt;BR /&gt;The client would like to continue the number in the new system. Therefore, e.g.: starting from 55001.&lt;BR /&gt;This also applies to the communication.Please also advise if any other sequence number need to be updated.&amp;nbsp;As I remember, there is a .sas file containing those numbers, which stored in the SAS application folder. please advise me&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 22 Sep 2017 04:50:41 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Customer-Intelligence/How-to-set-the-sequence-number-campaign-code-amp-communication/m-p/397984#M610</guid>
      <dc:creator>Amarnadh</dc:creator>
      <dc:date>2017-09-22T04:50:41Z</dc:date>
    </item>
    <item>
      <title>Re: How to set the sequence number campaign code &amp; communication code?</title>
      <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/How-to-set-the-sequence-number-campaign-code-amp-communication/m-p/397986#M611</link>
      <description>&lt;P&gt;Yes, the current sequence numbers are stored in a SAS dataset "MAMisc.Sequence" &amp;nbsp; MAMisc library is stored somewhere down the line from &lt;SPAN class="s1"&gt;sasconfig/Lev1/Applications/..., (the actual path changes with versions) and often times it is pre-assigned in your EG sessions (not always though).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="s1"&gt;It's the only place these numbers need to be updated, and in my opinion, it's relatively safe to do so. We have done such update from time to time (often it is needed when some migration is happening to avoid IDs overlapping).&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="s1"&gt;Make sure you don't screw up this dataset encoding (prefer in-place updates, try not to "rewrite" it completely unless you're certain there is no encoding mismatch) and don't leave it open in your EG session after the change - it will lock the dataset and you will be getting an error in SAS CI Studio doing things like campaign creation, runs, saves etc.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 22 Sep 2017 05:04:14 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Customer-Intelligence/How-to-set-the-sequence-number-campaign-code-amp-communication/m-p/397986#M611</guid>
      <dc:creator>Dmitry_Alergant</dc:creator>
      <dc:date>2017-09-22T05:04:14Z</dc:date>
    </item>
  </channel>
</rss>

