<?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 data droping on SAS CMS in SAS Customer Intelligence</title>
    <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/data-droping-on-SAS-CMS/m-p/575349#M1216</link>
    <description>&lt;P&gt;Why when I import data to SAs CMS it drops around 3% from it although the " hold out" is disable?&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 22 Jul 2019 12:46:58 GMT</pubDate>
    <dc:creator>Fdwa-Adwan</dc:creator>
    <dc:date>2019-07-22T12:46:58Z</dc:date>
    <item>
      <title>data droping on SAS CMS</title>
      <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/data-droping-on-SAS-CMS/m-p/575349#M1216</link>
      <description>&lt;P&gt;Why when I import data to SAs CMS it drops around 3% from it although the " hold out" is disable?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jul 2019 12:46:58 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Customer-Intelligence/data-droping-on-SAS-CMS/m-p/575349#M1216</guid>
      <dc:creator>Fdwa-Adwan</dc:creator>
      <dc:date>2019-07-22T12:46:58Z</dc:date>
    </item>
    <item>
      <title>Re: data droping on SAS CMS</title>
      <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/data-droping-on-SAS-CMS/m-p/575619#M1217</link>
      <description>&lt;P&gt;HI,&lt;/P&gt;
&lt;P&gt;Can you please clarify what you mean by import data ?&lt;/P&gt;
&lt;P&gt;and how have you determined that records are being dropped ? is it showing "XXXX dropped" on the communication node ?&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;James&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jul 2019 00:00:43 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Customer-Intelligence/data-droping-on-SAS-CMS/m-p/575619#M1217</guid>
      <dc:creator>JamesAnderson</dc:creator>
      <dc:date>2019-07-23T00:00:43Z</dc:date>
    </item>
    <item>
      <title>Re: data droping on SAS CMS</title>
      <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/data-droping-on-SAS-CMS/m-p/575649#M1220</link>
      <description>&lt;P&gt;using "import external node" node to import data (MSISDNs) form outside SAS, is always dropping X amount of MSISDNs, this not only when importing, when we do any campaign on SAS we fund that some customers who match the criteria were dropped, this when we don't enable the hold out.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jul 2019 05:51:49 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Customer-Intelligence/data-droping-on-SAS-CMS/m-p/575649#M1220</guid>
      <dc:creator>Fdwa-Adwan</dc:creator>
      <dc:date>2019-07-23T05:51:49Z</dc:date>
    </item>
    <item>
      <title>Re: data droping on SAS CMS</title>
      <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/data-droping-on-SAS-CMS/m-p/575680#M1222</link>
      <description>HI,&lt;BR /&gt;Sounds like this "import external" node is a custom node developed for your organisation, so you will need to check with your internal support team as to how it works. But in general the way that MA runs its queries against the database is that there is a "primary" table for each subject level, and this table must contain the entire universe of subject_ids (for you it seems that means MSISDNs). Each query from a campaign always joins to this primary table. So if you load a another table with an MSISDN that isn't in the primary table, it will get dropped.&lt;BR /&gt;Regards&lt;BR /&gt;James&lt;BR /&gt;</description>
      <pubDate>Tue, 23 Jul 2019 08:13:37 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Customer-Intelligence/data-droping-on-SAS-CMS/m-p/575680#M1222</guid>
      <dc:creator>JamesAnderson</dc:creator>
      <dc:date>2019-07-23T08:13:37Z</dc:date>
    </item>
  </channel>
</rss>

