New Recommendations for improving our self service portal reports created from a SAS EG project?

[JSJ]

Hi,

We write a very large amount of SAS EG reports,  migrating some to our SAS portal - Our self service site for our users to run their own reports. 

We accomplish this by creating stored procedures in SAS EG that are run as part of WRS.(SAS Web Reporting studio)

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.

Here are some of the reasons we are asking:

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.)

2. We often get requests for using an excel import file, which we don't know how to do with the current set up.

3. When we go to a new version of SAS, there are many moving parts that are not necessarily converted.

We have been doing the same process for over 6 years.  We are curious if there is a new way to accomplish this that is more streamlined and less time intensive.

Thanks!

[AlanC]

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).

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):

                StoredProcessService sp = SasLanguageService.StoredProcessService;
                sp.Repository = storedProcLibrary;
                sp.Execute(storedProcedureName, newParms);