The current Replace dialog is only regex search.  The text matching the regex pattern is replaced with the Replace with field literally.   The dialog should be improved to handle regex replacement as well.  Replace with: would allow find capture groups to be referenced as  $1, $2, $3, etc   For example, suppose I want to add square brackets around a sequence of consecutive digits.     Named capture groups should also be supported. For example:   Find: (?'digitrun'\d+) Replace: [${digitrun}]   The issue of no captures in replacement goes back to at least May 2017. See this post in communities    Because EG uses Enhanced Editor, the improvement should carry over into Windows SAS DM sessions.  If regex search and replace feature is not part of SAS Studio editor then that editor should be improved as well. ... View more

It'd be useful that the null device existed to access the null device of the OS, so we don't have to test whether nul (DOS) or /dev/null (Unix) are to be used.   ... View more

Adding the median to the periodic functions in VA would enable simple and effective median percentage growth capabilities. Since the mean and median are usually unequal in 'real world' data, this would be a huge add and time saver. ... View more

Please add a toggle switch that would alternate between displaying formatted and unformatted values in SAS data viewers.  Similar to the existing option to view Variable Names versus Variable Labels.  The current display always hows value labels and one has to resort to time-consuming tricks to unmask the relationship between value and format.  A simple toggle would permit a quick access to information hidden by the formatted values. ... View more

I would like the year,month and day to work on datetime variable as well as date variables. ... View more

It would be nice to have some dark or customizable themes for SAS Studio. Since it works in the browser some browser extensions can be used, but having customizable settings in the IDE would help for programmers moving from other IDE's.        ... View more

In SAS Studio, when you add a repository to the Git Repositories list of tracked repositories, it gives it a name that seemingly comes from the root folder the repository is stored in (the local disk folder, not the SAS Folder name). This name cannot be changed.   In my use case, all of my repos are stored in folders named the same thing - because they're in "[[project]]\src".  So I have all "src" repos, and can't change them.   It would be a better user experience if we either could relabel the repo while we add it (or afterwards), and/or if it defaulted to the SAS Folder Shortcut label if that is what it was added from.   Example: I have a SAS Folder shortcut named "MyProject" which points to //disk/MyProject/src/.  Right now, if I Open a Local Repository based on the repository that exists there, I will end up with a repository named "src".  It would be better to take the name from the SAS Folder shortcut, "MyProject", and further to allow me to relabel the repository with whatever makes sense - particularly as often Prod and Test will be identically named other than a higher level location difference. ... View more

It would be convenient to have an option in EG to have the log automatically scrolled to the bottom instead of the top after a program finishes running.   I'm usually most interested in seeing the bottom of the log rather than the top (e.g., to see the record count in the last table created, or the error message if an ABORT CANCEL was hit, etc.).   Following are screenshots showing the default behavior and the desired behavior.   The default behavior   The desired behavior     (Note:  This was originally posted as a question on the community forum at https://communities.sas.com/t5/SAS-Enterprise-Guide/Auto-scroll-to-bottom-of-log-in-SAS-Enterprise-Guide/m-p/730435/highlight/true#M38440)   Thanks,   Jake ... View more

I guess that there are many users who have to resort to using Excel or similar tools for data entry, as this is quite user-unfriendly to do in the current SAS frontends.   I therefore suggest creating a facility in Enterprise Guide and SAS Studio, similar to the old proc fsedit, for creating/editing SAS datasets. ... View more

Enough with all the crap with wrapping text automatically in ODS!    Just let us shut it off with something SIMPLE like WRAPTEXT=OFF!!! ... View more

When using pre-assigned libraries and right-clicking to display Properties, Enterprise Guide shows the storage path in metadata (/Shared Data/Libraries/.....). I would prefer to see the physical path of the library instead (as is shown for libraries assigned with the BASE engine). At least this should be a configurable option, or (ideally) both locations should be displayed. ... View more

I work with SAS EG 8.2. Please add the functionality that a new programm code is created as an external UTF8 *.sas-file by default. Maybe you need two options, one for internal/external, one for encoding. Today a new programm code (a) is created by default as an embedded code and (b) you can save it by default only into external as latin (SAVE AS from the embedded menu). ... View more

I'd like the ability to edit non .sas files in the SAS Studio editor.  e.g.   .txt .sh .php   etc...   Also, the ability to "save-as" as non .sas file would also be welcomed. ... View more

Add an ALLCHAR option to the PROC IMPORT statement -- to import all variables as character. This should apply to external text files and to Excel files (considering CSV files to be text files) This should not apply to external databases because they usually have metadata with predefined data-types.   The current situation is somewhat uncomfortable. The best option is to avoid PROC IMPORT in favor of the Libname statement with dbSAStype. This allows us to specify which fields should be character, but we have to specify each field individually. Another option is to use the Libname statement with Mixed=Yes, but this works only for columns that contain both numbers and words.   These discussions would probably benefit from the ability to import all variables as character: Reading in all numeric variables as character variables from .csv files Proc import excel - Default character How to get SAS to import MS xlsx files with date fields as all numeric (or all character) PROC IMPORT bug in 9.2? PROC IMPORT from Excel: how to ensure consistent types and formats for each data column ... View more

  In MySQL, you can use the group_concat function to concatenate across rows with a by group. I think this would be a valuable addition to the functions available in proc sql.     proc sql; create table EXAMPLE as select ID, STRING, group_concat(STRING) as ALL_STRINGS from DATA_SET group by ID; quit;     ... View more

the Current Visual Analytics 8.5 doesn't support on the Fly calculation on Reference line, not like other BI/Visualization are able to on the fly calculate the Average/Max/Min, but not hard code a number to the reference list.     ... View more

You can currently use the dataset option RENAME= to change the NAME used for a variable. It would increase flexibility if you could also change other attributes of the variables, such as the FORMAT, INFORMAT or LABEL using a similar syntax.  To avoid conflict with the existing LABEL= option for setting the member name and to follow a similar naming convention as the RENAME= option we might call these options REFORMAT=, REINFORMAT= and RELABEL=.  It should be possible to do it one both input and output dataset references.   Example: data want; set sashelp.class (reformat=(age=5.2)); run; Here is problem that made me think of this.  I was able to attach formats to variables being created with PROC TRANSPOSE by adding a FORMAT statement, but it generated WARNINGs in the log. 88 %let fmtlist=x xfmt. z zfmt.; 88 proc transpose data=have out=want(drop=_name_) ; 89 by id formset ; 90 id var_name; 91 idlabel var_label; 92 var var_value; 93 format &fmtlist; WARNING: Variable X not found in data set WORK.HAVE. WARNING: Variable Z not found in data set WORK.HAVE. 94 run; NOTE: There were 12 observations read from the data set WORK.HAVE. NOTE: The data set WORK.WANT has 4 observations and 5 variables. ... View more

It would be great if there was a function similar to N() that counted the number of non-missing character values. Currently SAS has functions for counting missing character (CMISS) and numeric (NMISS) variables, and nonmissing numeric variables (N). So this seems like a logical hole to fill.   This article suggests development is investigating the possiblity but I wanted to emphasize my interest and hopefull others will as well.   http://support.sas.com/kb/46/235.html ... View more

There are many fiddle websites that promote exchange of ideas and demonstrate sample code in a working environment.   There's a fiddle for that - https://fiddles.io - lists 40 or so, make a site so SAS can be added to the list.   If free to use sounds unpalatable, gate the site to SAS community accounts. Code the whole thing in SAS products because, well, ya got to "Eat your own dog food" (wiki)  Could be a wrapper app around a shackled but open SAS Studio login. ... View more