<?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: Derived Categorical Items in SAS Web Report Studio</title>
    <link>https://communities.sas.com/t5/SAS-Web-Report-Studio/Derived-Categorical-Items/m-p/14679#M149</link>
    <description>Thank you.  One question, how do you exptect the application to generate your "groupers"?</description>
    <pubDate>Wed, 11 Nov 2009 14:18:49 GMT</pubDate>
    <dc:creator>Jenn2</dc:creator>
    <dc:date>2009-11-11T14:18:49Z</dc:date>
    <item>
      <title>Derived Categorical Items</title>
      <link>https://communities.sas.com/t5/SAS-Web-Report-Studio/Derived-Categorical-Items/m-p/14678#M148</link>
      <description>Hi,&lt;BR /&gt;
&lt;BR /&gt;
Our users would really like to be able to derive new data items in WRS. Consider, a categorical item with 5,000 unique values. We can predefine several groupers in the Information Map but we will never cover all the possible combinations that users might want. If there was a CASE statement or some way of writing expressions, WRS would cover a lot more ground.&lt;BR /&gt;
&lt;BR /&gt;
One answer is to use EG rather than WRS but we're really keen on the web tool rather than the desktop tool. WRS is much easier to use for the bulk of our user community.&lt;BR /&gt;
&lt;BR /&gt;
Ian</description>
      <pubDate>Tue, 10 Nov 2009 13:56:48 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Web-Report-Studio/Derived-Categorical-Items/m-p/14678#M148</guid>
      <dc:creator>Ian</dc:creator>
      <dc:date>2009-11-10T13:56:48Z</dc:date>
    </item>
    <item>
      <title>Re: Derived Categorical Items</title>
      <link>https://communities.sas.com/t5/SAS-Web-Report-Studio/Derived-Categorical-Items/m-p/14679#M149</link>
      <description>Thank you.  One question, how do you exptect the application to generate your "groupers"?</description>
      <pubDate>Wed, 11 Nov 2009 14:18:49 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Web-Report-Studio/Derived-Categorical-Items/m-p/14679#M149</guid>
      <dc:creator>Jenn2</dc:creator>
      <dc:date>2009-11-11T14:18:49Z</dc:date>
    </item>
    <item>
      <title>Re: Derived Categorical Items</title>
      <link>https://communities.sas.com/t5/SAS-Web-Report-Studio/Derived-Categorical-Items/m-p/14680#M150</link>
      <description>I guess the user would be able to craft some "if then else" logic to define the values for the new item based on an existing data source column.</description>
      <pubDate>Fri, 13 Nov 2009 19:22:34 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Web-Report-Studio/Derived-Categorical-Items/m-p/14680#M150</guid>
      <dc:creator>Ian</dc:creator>
      <dc:date>2009-11-13T19:22:34Z</dc:date>
    </item>
    <item>
      <title>Re: Derived Categorical Items</title>
      <link>https://communities.sas.com/t5/SAS-Web-Report-Studio/Derived-Categorical-Items/m-p/14681#M151</link>
      <description>Ian, &lt;BR /&gt;
&lt;BR /&gt;
You might be able to accomplish this using a SAS Stored Process and utilizing within the Information Map. The SAS Stored Process could define a custom format that the Information Map will then utilize, or some case logic to set within the initial query.&lt;BR /&gt;
&lt;BR /&gt;
I don't believe there is a way to complete this within the Web Report Studio technology without incorporating some SAS coding skills.&lt;BR /&gt;
&lt;BR /&gt;
Angela Hall&lt;BR /&gt;
Zencos Consulting&lt;BR /&gt;
&lt;A href="http://www.zencos.com" target="_blank"&gt;http://www.zencos.com&lt;/A&gt;</description>
      <pubDate>Wed, 18 Nov 2009 03:35:25 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Web-Report-Studio/Derived-Categorical-Items/m-p/14681#M151</guid>
      <dc:creator>AngelaHall</dc:creator>
      <dc:date>2009-11-18T03:35:25Z</dc:date>
    </item>
  </channel>
</rss>

