When creating a stored process from a flow, include the name of the project and process flow into the comments so that it can be traced/tracked back to the original project. ... View more

SAS users around the word use many modules like SAS Studio, EG, EM, DI etc.    Most of these applications show the status of executing the program or project or flow but none of them shows the progress bar with real-time information about code/project/program estimated execution time. It will be very helpful for all to implement that feature in SAS applications like EM, EG, DI and others.     ... View more

Due to cybersecurity restrictions, our SAS Site Administrators have enforced system options like SOURCE, SOURCE2 and MPRINT on every SAS session to make sure that every single line of submitted code is printed on the SAS Log. Options SOURCE and SOURCE2 pose no particular problem.  But a locked-in MPRINT option has the unwanted effect of multiplying the number of lines of Macro Code being printed on the Log, every time a Macro is invoked. Having a system option that displays the Macro Code only once (regardless of how many times the Macro is called in the program) would be very helpful to reduce the number of lines displayed on the Log. MPRINT is a debugging option that works well as it does. The new option could be named somewhat differently (maybe MLOG ?). ... View more

We would like to be able to schedule a report job that will automatically run an existing dashboard, convert  it to PDF, and save the PDF to a network location.   Currently we are using the SAS PowerPoint Add-In to import data from the dashboard into PowerPoint.  This is very inefficient and takes a long time if the network is busy. ... View more

Please enhance / fix the Stored Process Prompts especially when there are dependencies between the prompts.  Our team have raised multiple issues with SAS Support about prompts not displaying default values (even when the default values are checked) or unwanted "warning" messages that confuse our users who think an error is happening.  We need more control over the look and feel of the interface or else we would like SAS to improve it.  We are not interested to migrate all our Portal reports to SAS VIYA.  Thank you. ... View more

At the top of my stored procedure I have code that checks prerequisites for it to run successfully, and if I find any issues I want to return a custom error message, and then end the stored process gracefully.  Something like "endsas" but without the error conditions associated with it.   I saw SAS Note: http://support.sas.com/kb/16/225.html  which gives a workaround but it involves disabling the "Show Log" button across all stored processes which I do not want to do.   ... View more

When running a SP in Excel, there should be one worksheet generated for each output of the SP, not just concatenated within a single worksheet.  So, if a SP has 3 proc prints, there should be 3 separate worksheets. ... View more