<?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 New Recommendations for improving our self service portal reports created  from a SAS EG project? in SAS Enterprise Guide</title>
    <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/New-Recommendations-for-improving-our-self-service-portal/m-p/709341#M37932</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;We write a very large amount of SAS EG reports,&amp;nbsp; migrating some to our SAS portal - Our self service site for our users to run their own reports.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We accomplish this by creating stored procedures in SAS EG that are run as part of WRS.(SAS Web Reporting studio)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We would like to know if there is an updated recommendation making this process easier or creating a new self service site for our users.&lt;/P&gt;
&lt;P&gt;Here are some of the reasons we are asking:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1. It takes many steps involving 3 sets of employees to accomplish loading a report to the portal. (We design the report and the WRS setup, IT has to migrate the stored procedure, our management has to add the link to the portal.)&lt;/P&gt;
&lt;P&gt;2. We often get requests for using an excel import file, which we don't know how to do with the current set up.&lt;/P&gt;
&lt;P&gt;3. When we go to a new version of SAS, there are many moving parts that are not necessarily converted.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have been doing the same process for over 6 years.&amp;nbsp; We are curious if there is a new way to accomplish this that is more streamlined and less time intensive.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks!&lt;/P&gt;</description>
    <pubDate>Mon, 04 Jan 2021 22:55:35 GMT</pubDate>
    <dc:creator>JSJ</dc:creator>
    <dc:date>2021-01-04T22:55:35Z</dc:date>
    <item>
      <title>New Recommendations for improving our self service portal reports created  from a SAS EG project?</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/New-Recommendations-for-improving-our-self-service-portal/m-p/709341#M37932</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;We write a very large amount of SAS EG reports,&amp;nbsp; migrating some to our SAS portal - Our self service site for our users to run their own reports.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We accomplish this by creating stored procedures in SAS EG that are run as part of WRS.(SAS Web Reporting studio)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We would like to know if there is an updated recommendation making this process easier or creating a new self service site for our users.&lt;/P&gt;
&lt;P&gt;Here are some of the reasons we are asking:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1. It takes many steps involving 3 sets of employees to accomplish loading a report to the portal. (We design the report and the WRS setup, IT has to migrate the stored procedure, our management has to add the link to the portal.)&lt;/P&gt;
&lt;P&gt;2. We often get requests for using an excel import file, which we don't know how to do with the current set up.&lt;/P&gt;
&lt;P&gt;3. When we go to a new version of SAS, there are many moving parts that are not necessarily converted.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have been doing the same process for over 6 years.&amp;nbsp; We are curious if there is a new way to accomplish this that is more streamlined and less time intensive.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 04 Jan 2021 22:55:35 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/New-Recommendations-for-improving-our-self-service-portal/m-p/709341#M37932</guid>
      <dc:creator>JSJ</dc:creator>
      <dc:date>2021-01-04T22:55:35Z</dc:date>
    </item>
    <item>
      <title>Re: New Recommendations for improving our self service portal reports created  from a SAS EG project</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/New-Recommendations-for-improving-our-self-service-portal/m-p/709343#M37933</link>
      <description>&lt;P&gt;I roll my own web reporting site, have the users store the programs in a directory, then execute them using SAS Int Tech. SAS Int Tech can access stored procedures (just some SAS code with a header/footer added in).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For web-based work, I use ASP.NET Core (now .NET 5). The C# code needed to execute the stored procedures is not bad (here is the gist):&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;                StoredProcessService sp = SasLanguageService.StoredProcessService;
                sp.Repository = storedProcLibrary;
                sp.Execute(storedProcedureName, newParms);
&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 04 Jan 2021 23:07:23 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/New-Recommendations-for-improving-our-self-service-portal/m-p/709343#M37933</guid>
      <dc:creator>AlanC</dc:creator>
      <dc:date>2021-01-04T23:07:23Z</dc:date>
    </item>
  </channel>
</rss>

