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

The where functions are perfectly valid so why red?   proc tabulate data=lib.test; class period_end; tables period_end; where period_end > '01jan19'd; run; proc freq data=lib.test; tables period_end; where period_end > '01jan19'd; run; ... View more

Today the 'history gets cleared when data is recreated.   When viewing data it would very nice if EG could remember previous used where clauses in the current EG Session – even when data is updated (re-run) or even used on another dataset (cross-data-use).       ... View more

Add a DESC= to allow user-coded description value to as many "proc-level" (i.e. DATA step, PROC xxxxx, possibly ODS ) statements as possible.   Add an option to add this descriptor to some SASLOG messages such as at the end of DATA or PROC when showing CPU use. z/OS specific, add this value to the SAS SMF record. The intent is to allow "grouping" of pieces of a program, to easier identify the parts that error messages come from, or analysis of resources used,  with a value of meaning to the user. Such as "summarization and redistribution of sales by region"  which might consist of many different DATA and PROC actions but be one logical piece to the user. ... View more

The format $QUOTE will enclose the value in double quote characters and properly handles doubling up any embedded double quote characters..  It would be useful to have a format that would generated a quoted string using single quote characters.  String literals quoted using single quotes will suppress any embedded macro triggers and can be used in pass-through SQL code.   Perhaps they could add a letter to the end of the format name like they have done with the date formats. ... View more

In Enterprise Guide, Server List, when opening a server, the files section and the entries below it should have the Properties option activated when right-clicking, and at least display the physical file(directory)name when selected. This would aid users in finding their files within the server's filesystem, especially when the location of the home directory or the root navigation folder of the workspace server has been changed from the default. Additional information (ie from a quick ls -l in UNIX) would be appreciated. ... View more

The datetime output is identical to that of the E8601DTw.d format except for the T separator.    "yyyy-mm-dd hh:mm:ss.ffffff"  instead of  "yyyy-mm-ddThh:mm:ss.ffffff"   A format generating the same output for date (and time?) variables would be useful too as some tools like Impala can only use timestamps, not dates.   I know this can be done using a picture format. Doing so makes the code a lot less portable though.   ... View more

Currently in SAS Studio, under Preferences -> Editor, there is an option for font size but not the font typeface. It would be great if the user can change the font type face. The current font is a bit too thin. I prefer Consolas.   P.S. I did not find SAS Studio to be an Idea Label so I listed this under SAS Visual Analytics. Please move this if not in the right category. THanks. ... View more

In SAS Visual Analytics it should be possible to print large list tables or crosstab on several pages to a PDF document. Currently every table is printed on one page. A feature to split a table on more than one page is required. ... View more

SAS Studio beginning in version 3.4 now allows to create visual  Process Flows, like SAS Enterprise Guide. The Process flows are stored into a *.CPF file based on Apache VTL (Velocity Template Language) - it seems. On the other hand, SAS EG flows are stored into a proprietary Zip archive called Project file (*.EGP file) internally using XML for flow description.   At this point, there is no automatic conversion tool available between SAS EG *.EGP format flows and SAS Studio *.CPF flows. It would be definitively useful to provide one to the users or to the admins. Even partial conversion would be fine, taking into account differences between the to clients. Re-creating manually SAS EG jobs into SAS Studio would be time-consuming, costly and error prone.   As a side note, SCAPROC Procedure (the engine running the SAS EG Code analyser feature) has no 'reverse' capacity enabling a SAS EG process flow to be converted back into some Universal and/or portable description code (XML, VTL etc.). It can ony convert user-written code into SAS EG Flows. SAS Studio Process flow designer has neither capacity, for the moment. ... View more

Currently the Change Data Source facility in SAS Visual Analytics affects all objects using that Data Source in a given Report.   I think that the Change Data Source facility should be amended so that it can be applied to individual objects within a Report, not just the entire Report.   I propose that when a user invokes the Change Data Source facility, a dialog box is presented to the user that lists all objects in the current report and, alongside each object, its data source. The user can then choose the individual objects that they want the data source change to apply to, or they can choose a Select All option, which is what they get at  present.   The workarounds and wasted effort currently required to simply change the data source used by a given object, say a Cross Tab within a Report, is just another reason for people to avoid using SAS Visual Analytics. It makes life too hard for a new starter and just puts them off. Fixing this anomaly will get more people to love VA......even more 😎.   Cheers,   Downunder Dave Wellington     ... View more

Add Shewhart Charts as a template within VA for automatically generating control charts for dashboards ... 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 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 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

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

    As a SAS Studio user, I want SAS to provide an update to SAS Studio that will make the browser provide notification when a job is complete. This feature is needed to improve the user experience for the SAS Studio product.   Example: Many times we must run programs or projects which take a considerable amount of time to complete. Due to unknowns such as server and database usage, the job may take much longer or shorter. Since SAS Studio does not provide visual feedback on the task bar, the only way to check if anything has changed, is to open the Studio window and visually inspect if it is still running. Many windows applications (including web-apps) provide a blink or highlighting feature on the task bar for the application to indicate something has changed in the application or some input is needed. I would like Studio to implement this sort of 'blink' effect when a job or project run has been completed.   We are currently on 9.4m6, Studio 3.8.  ... View more

Hi,   the idea is to allow for the SET statement to use observation's number(curobs) in the where clause and where=() dataset option. So the following query on the data set's engine level would be possible:   data out1; set sashelp.class curobs=co; where age>12 and co<10; run; data out2; set sashelp.class(curobs=co where=(age>12 and co<10)); run; with expected output equivalent to: data out3; set sashelp.class curobs=co; if age>12 and co<10; put (_ALL_) (=); run; The key idea is that it would be possible on data engine level, so before PDV.   All the best Bart     ... View more

It would be cool if a proc existed that output macro documentation of a compiled macro. Kind of like Proc Catalog but in addition to the current fields it provides – it included a more robust description (more than 40 characters) and included the list of keyword or positional parameters. Maybe even info like if the parameter is required, optional, default value if defaulted, example value, and an example macro call. Similar to Proc Contents where you can turn on/off the level of details requested - you can get a high-level list of tables & their values, and a detailed page of each individual table. It would be helpful if something similar existed for compiled macros. ... View more