<?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: After SAS Code Node Variables Disappear- Rather, Never Appear in SAS Data Science</title>
    <link>https://communities.sas.com/t5/SAS-Data-Science/After-SAS-Code-Node-Variables-Disappear-Rather-Never-Appear/m-p/208131#M2826</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think that is all correct.&amp;nbsp; If you click on the SAS Code node, then click on the ellipsis button for Exported Data from the Properties panel, you can see from there whether your variable is being picked up correctly.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;IMG alt="ExportedData.png" class="jive-image" src="https://communities.sas.com/legacyfs/online/9706_ExportedData.png" /&gt;&lt;/P&gt;&lt;P&gt;Click on the row for TRAIN, then the Properties... button. On the Variables tab, you should see your new variable listed as a Target.&amp;nbsp; I'm guessing it's the case that the Text Parsing node only displays variables with a particular role, but not sure why you wouldn't see it for Decision Tree.&amp;nbsp; Anyway, confirming that it shows up here is the first step.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 23 Mar 2015 20:26:25 GMT</pubDate>
    <dc:creator>WendyCzika</dc:creator>
    <dc:date>2015-03-23T20:26:25Z</dc:date>
    <item>
      <title>After SAS Code Node Variables Disappear- Rather, Never Appear</title>
      <link>https://communities.sas.com/t5/SAS-Data-Science/After-SAS-Code-Node-Variables-Disappear-Rather-Never-Appear/m-p/208130#M2825</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ladies &amp;amp; Gentlemen,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pretty simple - I start with a data file. I then attach a SAS Code Node to it for bucketing a continuous variable into four discrete ordered buckets. I can view and Edit most of the variables in both the data node and in the Code Node. The only variable I cannot see or edit is the newly created one. [Previously any of this bucketing I would do in Enterprise Guide then re-read the data into Enterprise Miner.]&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Next I attach a Text Parsing node to the Code Node. When I go to Edit Variables in my Text Parsing Node only my text field shows up. But I &lt;SPAN style="text-decoration: underline;"&gt;&lt;SPAN style="color: #575757; text-decoration: underline;"&gt;think&lt;/SPAN&gt;&lt;/SPAN&gt; the rest of the variables are there. So if I attach a Decision Tree Node next all of the variables except for my newly created on are there.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Should I do something different with my Code Node? I am including the code below for your convenience. Any recommendations of adjusting my code to make the new data field show like the rest would be great. Thank you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;proc format;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&amp;nbsp; value F_TOTALRESERVES_B&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0 -&amp;lt; 300 = 1&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 300 -&amp;lt; 1500 = 2&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1500 -&amp;lt; 10000 = 3&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10000 - high = 4;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;run;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;data &amp;amp;em_export_train;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&amp;nbsp; set &amp;amp;em_import_data;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&amp;nbsp; TOTALRESERVES_B = put(TOTALRESERVES, F_TOTALRESERVES_B.);&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;run;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;%EM_METACHANGE(&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&amp;nbsp; NAME = TOTALRESERVES_B,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&amp;nbsp; LEVEL = ORDINAL,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;&amp;nbsp; ROLE = TARGET&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;);&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Mar 2015 18:26:06 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Science/After-SAS-Code-Node-Variables-Disappear-Rather-Never-Appear/m-p/208130#M2825</guid>
      <dc:creator>Zachary</dc:creator>
      <dc:date>2015-03-23T18:26:06Z</dc:date>
    </item>
    <item>
      <title>Re: After SAS Code Node Variables Disappear- Rather, Never Appear</title>
      <link>https://communities.sas.com/t5/SAS-Data-Science/After-SAS-Code-Node-Variables-Disappear-Rather-Never-Appear/m-p/208131#M2826</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think that is all correct.&amp;nbsp; If you click on the SAS Code node, then click on the ellipsis button for Exported Data from the Properties panel, you can see from there whether your variable is being picked up correctly.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;IMG alt="ExportedData.png" class="jive-image" src="https://communities.sas.com/legacyfs/online/9706_ExportedData.png" /&gt;&lt;/P&gt;&lt;P&gt;Click on the row for TRAIN, then the Properties... button. On the Variables tab, you should see your new variable listed as a Target.&amp;nbsp; I'm guessing it's the case that the Text Parsing node only displays variables with a particular role, but not sure why you wouldn't see it for Decision Tree.&amp;nbsp; Anyway, confirming that it shows up here is the first step.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Mar 2015 20:26:25 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Science/After-SAS-Code-Node-Variables-Disappear-Rather-Never-Appear/m-p/208131#M2826</guid>
      <dc:creator>WendyCzika</dc:creator>
      <dc:date>2015-03-23T20:26:25Z</dc:date>
    </item>
  </channel>
</rss>

