Request: Please can SAS include the option to calculate test statistics for the unadjusted and stratified MN method.   Background: Miettinen-Nurminen (MN) methods are increasingly being requested by regulatory agencies. This is particularly relevant for non-inferiority trials where it's appropriate for the variance to be estimated under the null hypothesis. Within the PROC FREQ procedure, it's currently possible to calculate the treatment differences (and CIs) for both the unadjusted MN and the stratified MN methods as well as other MN tests such as the Summary Score method (also referred to as Agresti Score). However, whilst for the Summary Score method SAS allows the option to calculate the test statistics this is not yet available for the unadjusted MN method or the stratified MN method.   These methods are important as they estimate variance under the null hypothesis, specifically the test statistics are of particular useful for: testing superiority and presenting a p-value studies with interim analyses, particularly when multiplicity is controlled via a group sequential design i.e. with alpha boundaries less than the typical 1-sided 2.5%/2-sided 5% alpha Example SAS code (for reference): Note: data not supplied due to proprietary nature, however code shared to illustrate current options/limitations.  The unadjusted MN treatment difference can be calculated using: proc freq data=DATA; tables TRT*AVAL / riskdiff(CL=(MN) noninferiority margin=0.1);  run; Note: whilst the (unadjusted) Wald test statistics are calculated, it would be helpful if the unadjusted MN test statistics could also be provided. The stratified MN Score treatment difference can be calculated using: proc freq data=DATA; tables STRATA*TRT*AVAL / riskdiff(CL=(MN) noninferiority margin=0.1) COMMONRISKDIFF(CL=(MN score) test=(score)); run; Note: whilst the (adjusted) Summary Score (also referred to as Agresti Score) test statistics are calculated, it would be helpful if the stratified MN test statistics could also be provided. Specifically, if MN could also be an option within COMMONRISKDIFF(TEST=( )) ... View more

We have a use case where our company files are stored in Sharepoint. It is currently difficult to access these files on VIYA and they manually have to be uploaded. We would like to be able to connect SharePoint to VIYA such that: 1. SharePoint files and folders are visible in SAS Studio Explorer folder tree and can be manipulated like standard files residing on the SAS Server. 2. SharePoint files are directly accessible to SAS Studio flows.     2.1.Allow a file residing in SharePoint to be imported/exported using the standard SAS Studio Import/Export functions.     ... View more

Frequently a SAS programmer needs to both sort and divide a dataset. Typically these tasks are satisfied via a two stage program:   (1) divide the dataset, (2) sort the parts. Something like:   data _asia (where=(origin='Asia')) cars_europe (where=(origin='Europe')) cars_usa (where=(origin='USA')) /view=_asia; set sashelp.cars; run; proc sort data=_asia out=cars_asia; by msrp; run; proc sort data=cars_europe; by msrp; run; proc sort data=cars_usa; by msrp; run; Enabling proc sort to do both of these tasks (with syntax such as below) would often significantly reduce input/output activity, and offer a bit of code simplification:  proc sort data=sashelp.cars out=cars_asia (where=(origin='Asia')) cars_europe (where=(origin='Europe')) cars_usa (where=(origin='USA')) ; by msrp; run;   Of course, the multiple output datasets need not be mutually exclusive like the example above. ... View more

We would like the ability to save/export a Studio flow as a .sas external file. To be able to specify the path and filename.   We are migrating from Enterprise Guide and this is a critical feature that is used extensively by many users to export process flows and execute the resulting .sas in a batch environment. We intend to follow the same way of working in SAS Viya/Studio. ... View more

In large enterprise organizations, it would be beneficial to be able to hide, or make visible, folders from the SAS server files that are mounted from the Studio Explorer pane based on the groups the users are in.   See Case: CS0115567 for the original support question and example. ... View more

It seems proc import can retrieve data from Excel if the data is in a sheet by itself using the "sheet=" statement, known range i.e., "A1:C10", or named range using the "range=" statement.  What I don't see is an easy way to import the data if it is an Excel Table.  Something like a "table=" statement in the code below to accomplish this would be extremely helpful.  I apologize if this already exists, I couldn't find anything.  Thanks in advance for your attention to this matter.   proc import out= WANT datafile= "C:\ExcelFile.xlsm" dbms= EXCEL replace; TABLE= "TBL"; run; ... View more

SAS Studio currently supports text, xml and python files in conjunction to the SAS program format.  Markdown is a widely used text markup format used in repositories of source code to document the functionality of a project and have the markup rendered in a variety of file formats such as HTML, LATEX, PDF etc.  Markdown files are used widely in git hosted repositories and is a defacto standard within the community.  Currently, if a user tries to open a markdown file, the user will be prompted to download the file instead of opening within the application.  This stops users from being able to effectively view git repository help docs or create developer and api documentation for SAS projects without leaving SAS Studio and using some other third party application.   Ideally SAS Studio would allow the following: Viewing of Markdown files with syntax highlighting of markdown elements View rendered markdown as html in a separate tab similar to results rendering currently used for ODS Allow creation and editing of files in markdown format with syntax highlighting. ... View more

EG should update the program icon (highlighted below) at the same time the process flow program icon is updated. Using example in screen shot, blue circle should changed to a red X at the same time the process flow program icon changes. The Log Summary is also not updated while a program is running. Both features are incredibly helpful due to the notification of errors/warnings prior to completion, and were present in EG 7. ... View more

To be consistent with those longtime users coming from the SAS 9.4 world, it would be very useful to have an option to append to the results window rather than replace its contents when resubmitting a program or a portion of a program.  I see that SAS Studio 3.8 added an option to append to the log window rather than replace and it would be great to have a similar option for the results window.  We will soon be moving to SAS Viya so I'm of course most interested in this being implemented in the latest release of SAS Studio running under Viya. ... View more

SAS is responsible for a huge number of users in our organization, and there is not an easy way for administrators to post messages to users upon connection to our back end services across all the various UI's.  It would also be nice to have a "stub" service that could be left running for maintenance notification.   It would be good upon connection to a Meta server to have a way to post a message before, and after authentication in a standard way. It would also be good to provide real-time announcements.   Message pre-authentication: "There will be maintenance on Saturday from 4:00pm to 7:00am."  Message post-authentication: "Due to issues with the NAS interface, there may be slow connections when browsing the file system." Real time/Flash messages: "The system will go down in 45 minutes for patching."   (in this scenario it would be nice to stop allowing new connections, and then gracefully quit running sessions to acquiesce)   It would also be nice to provide a system is down for maintenance message.   Perhaps the client could default to checking a simple web service on the meta server for maintenance notification.   HTTP/HTTPS providing a response of: Maintenance: "The SAS environment is currently down for maintenance; SAS will be available by 7am ET."   Client could show "The SAS environment is currently down for maintenance; SAS will be available by 7am ET."   If you use a simple HTTP/HTTPS interface, then you can use a DNS failover or a simple web service on the host to provide information when the service is down.  (Even a simple Python http service 'cd /sas/maintenance; python -m SimpleHTTPServer 80') ... View more

By default, PROC REPORT suppresses repeated values of group variables. This is very handy most of the time, but it would be really nice to have an option to display the value of the group variable on every row. There is a simple workaround, but when you have many group variables you can easily end up with four or five compute blocks and a slew of duplicate variables.   Example Data:   data example; input chargrp $ numgrp chargrp2 $ value; datalines; grpa 1 grpx 5 grpa 2 grpx 23 grpa 1 grpy 15 grpa 2 grpy 2 grpb 1 grpx 13 grpb 1 grpy 11 grpb 2 grpy 12 grpb 2 grpy 34 ; run;   Default Functionality:   proc report data=example; column chargrp numgrp chargrp2 value; define chargrp / group; define numgrp / group; define chargrp2 / group; define value / sum; run;   Current Workaround:   proc report data=example; column chargrp numgrp disp_numgrp chargrp2 value; define chargrp / group; define numgrp / group noprint; define disp_numgrp / "NUMGRP" computed; define chargrp2 / group; define value / sum; compute chargrp; if not missing(chargrp) then hold_chargrp = chargrp; else chargrp = hold_chargrp; endcomp; compute disp_numgrp; if not missing(numgrp) then hold_numgrp = numgrp; disp_numgrp = hold_numgrp; endcomp; run;   Desired Functionality:   proc report data=example repeatgroupval; column chargrp numgrp chargrp2 value; define chargrp / group; define numgrp / group; define chargrp2 / group; define value / sum; run; /* or */ proc report data=example; column chargrp numgrp chargrp2 value; define chargrp / group repeatval; define numgrp / group repeatval; define chargrp2 / group; define value / sum; run;    P.S. I'm surprised this hasn't been suggested already, but I couldn't find it anywhere. If it has already been suggested, feel free direct me to that post and mark this as a duplicate. ... View more

When running below code more than once in a session I'm getting a warning that I can't suppress. proc fcmp outlib=work.funcs.demo; function demo(in); out=in+1; return (out); endsub; run; option CMPLIB=work.funcs; data _null_; xx=demo(5); run; WARNING: Function 'demo' was defined in a previous package. Function 'demo' as defined in the current program will be used as default when the package is not specified. What I would like as an extension to PROC FCMP are two new options: NOWARN:  Suppress above warning and write a NOTE instead. NOREPLACE: To not replace the already compiled function. Write a NOTE that the function already exists and won't be replaced. ... View more

Hi, I think that SAS Visual Analytics be enhanced to provide for up to three title lines on an object.   Under SAS Visual Analytics 8.5.2 we are only allowed to define a single title linefor a report object, such as a bar chart.   Whilst I know that titles should not be very wordy, sometimes it helps to have a little explanatory text as line #2 or even line #3 of a title.   At the moment I am stuck with something like the following screenshot of a chart using my favourite made-up data. The title for the report could be made more informative if the text could be split across several lines as I wanted them to be, not just auto-wrapped.     Vote for this fantastic idea, please ! Anything that encourages more people to use SAS Visual Analytics for more things, can't be all bad, right ?   Downunder Dave Wellington         ... View more

As far as I understand, there is currently no option to use explicit pass-through with cloud data exchange. This is a major drawback for customers migrating to Viya, that over the years have made extensive use of this functionality on the SAS 9.4 environment. One of the main reasons explicit pass-through has been used, is to make use of non-standard SQL functions available from the database vendor. One such function that will require a lot of rewriting of code is the Qualify-statement available at several vendors.    Thanks in advance for your attention to this matter. ... View more

PROC IMPORT uses n GUESSINGROWS ( default 20, can be set to whatever ) from the DATAFILE to determine if the OUT dataset columns should be numeric or character.  Many numeric account numbers ( e.g. credit cards ) are 16 digits in length which exceed the max value for an 8 byte numeric column of 9,007,199,254,740,992.  As a result the large numbers are not imported accurately. Since the DATEFILE is being parsed to GUESSINGROWS depth in any case, the max value could be known from the rows examined.  If the max value is > 9,007,199,254,740,992 PROC IMPORT could set the data type in the column to character to ensure all digits are retained. ... View more

I have two ideas for SAS Visual Analytics "Distribute reports" feature.    Ability to change the font (or any images) in the email that is sent with the distribution, and Ability to copy a list of recipient emails especially the feature will be useful if it is a large list of emails   Thanks ... View more

Hi,   We are facing a strong showstopper with the current limitation of not allowing to mix INNER and OUTER joins in queries. Which is impacting the usage of our data providing system, to which SAS connects to.   Giving more options in the "libname jdbc" statement would give the user the ability to "match" the query generation in SAS with the real capacity of the underlying system using JDBC.   Here are a few of those options that would be nice to add: - underlying system supports using inner and outer joins together - this limitation in particular is much more impactful than the others. Most DBMS systems allow that today so SAS should allow that for JDBC datasources. - underlying system does not support JDBC escape sequences - pass custom connection properties (Mapping for java class Properties) - sometimes some JDBC drivers do not support passing all parameters as URL.   Thank you ! ... View more

It would be nice to have a way to set the order of the variables in the output data set based on the order of the variables listed in a KEEP= data set option.  I apologize if this already exists, I did a quick Google search and the only ways I see to achieve this is by using RETAIN, FORMAT, etc. before the SET statement, like in the below code.  It is not a huge lift to list the variables twice, it just seems redundant.  The second data step below demonstrates one way this could be done.   Thanks in advance for your attention to this matter. data WANT (keep= ID DATE ORDERNUM AMT); retain ID DATE ORDERNUM AMT; set HAVE; run; data WANT (keep= ID DATE ORDERNUM AMT / inorder); set HAVE; run; ... View more

When you run a sas program in STUDIO, in the log you have a summary of ERRORS/WARNINGS/NOTES that you can use to navigate the log, as shown in the highlighted red box in the screenshot.     If you run that same sas program as a background submit it creates a log, however, when you open that log the ERRORS/WARNINGS/NOTES summary does not exist.     In EG, if you open a saved log it will parse the file and provide you with the summary you can then use to jump around in the log. The below screenshot is from a saved log that was then drag and dropped into an EGP and you can see that it provides you with the summary.     Can this funcitonality be added to SAS STUDIO so that when viewing saved SAS logs (such as the one created by a background submit) the "log summary" is available?   Note: this suggestion is related to the question asked in this thread https://communities.sas.com/t5/SAS-Studio/For-saved-logs-is-it-possible-to-get-a-ERRORS-WARNINGS-NOTES/m-p/852197/highlight/false#M10742   Thanks   ... View more