In SAS EG 6.1 when descriptions for prompts are displayed they're not always wrapped which results in the description not being visible to users. I've noticed this issue seems to only happen with my date prompts. Maybe this is a bug? I've attached a screenshot where the description for the first three prompts are displayed correctly and the last is not displayed correctly (circled in red).    Thanks! -riley ... View more

Adding a new color scheme to EG which mitigates the eye strain caused by light colored backgrounds would be much appreciated. Black or dark background with the colorized varying file elements in order to maintain the ease of reading one's  own code or someone else's is the preference (note: "High Contrast" is not acceptable. ... View more

Syntax CALL PUTC(c-source, format <, new-string <, return-code >> ) CALL PUTN(n-source, format <, new-string <, return-code >> ) Arguments c-source specifies a character constant, constant, variable, or expression to which you want to apply the format.     n-source specifies a numeric constant, constant, variable, or expression to which you want to apply the format.     format contains a string with the SAS format that you want applied to the value that is specified in the source. ...   new-string specifies a character variable in which to place the formatted value.   return-code specifies a numeric variable for which received a return-code of 0,1 or 2 0 - No error 1 - no-match 2 - format not found (or more) Example: proc format; value $A '00' ="00" '01','04'="foo" '02' ="bar" '03' ="sna" ; data result; do x = '00', 'AA'; call putc(x, "$A.", y, rc); if rc ne 0 then call missing (y); output; end; run;   result: x y 00 00 AA   ... View more

Add "Do Not Run" to the "Based on" list in the dialog "Add (Edit) a Condition".  Let this add a "Do Not Run" to the list under "If this condition is true:".  If this is the only condition then the program node does not run.  Let this be equivalent to a condition based on a macro variable "If this condition is true: 1 equal to 0" or: %if 0 %then %do; The "Conditional Processing" dialog is accessed when adding a condition to a node in a EG program node or other object.  When using the Add (or Edit) button a dialog titled "Add (Edit) a Condition" appears.  This dialog has a list named "Based on".   I rarely use Conditional Processing... but when I do, I use it to exclude a node, or branch, from being run.  This change helps communicate intent "not to run" a particular object rather than using another means that is intended to communicate that there is a variable condition that might change dependent on some change of a value.  Currently I use this hack, to do this: I add a condition to the node, make it based on a macro variable and fill out the as show below.  It appears in the "Conditional Processing" as "1 equal to 0":   macro variable: 1 operator: equals value: 0   See the attachment  Do_Not_Run_Program(3).egp.zip (28 KB) which is a an EGP file (change the extension back to EGP).     Its noted that this isn't how Conditional Processing was meant to be, but I find use in it.  I hope you consider it. ... View more

SAS EG needs functionality to: 1. convert (consolidate) groups of ETL process flow steps into programs without having to export (and vice versa - see 2.) 2. expand program code so it can be viewed as individual steps in the ETL process flow window 3. view the code for the entire project in one window, which should change in line with edits in the process flow/ query editors and vice versa - this is vital so that users aren't forced to view snippets of code by constantly opening and closing query steps in the process flow window.   Reasoning: Currently viewing SAS code in SAS EG is all broke up into little pieces. This is forced by the design of SAS EG. However, Base SAS users are familiar with editing code down the page in a single editor window. Even though SAS EG users might find ETL (drag and drop) style editing of steps in the process flow window simple. It is difficult for Base SAS users to move across to SAS EG. The code of each of the programs and ETL process flow steps in any particular project are still not well integrated into a single window. These limitations hamper quality assurance review of work by different colleagues within an organisation because different working styles are not well accounted for in SAS EG. Notwithstanding that SAS EG allows users to either export code from a process flow or to view the code of individual programs or of individual process flows separately, there is still no single location for the code of the entire project to be viewed in one editor window like in Base SAS. Implementing the suggestions above would help Base SAS users to work with SAS EG and allow different users to integrate their working styles together more easily. ... View more

In the new EG 8, you cannot use any of these options without creating a project. I would really like the ability ... View more

Add an option /RETAIN to the SET statement which would command SAS not to clear the program data vector (PDV) prior to each dataset read.    Example: data Whole: set Left Right Center /Retain; BY v1; run; "Left" dataset: v1 v4 A998 Q "Right "dataset: v1 v2 A998 06/01/18 B027 05/21/18 E001 03/31/18 F221 11/01/17 C379 10/07/17 G693 06/19/18 "Center" dataset: v1 v3 A998 Z A998 Y A998 X A998 W B027 V C379 U D032 T The result with the proposed /RETAIN option.  The bolded values are "retained" from the PDV unchanged from the prior observation: v1 v4 v2 v3 A998 Q . A998 Q 06/01/18 A998 Q 06/01/18 Z A998 Q 06/01/18 Y A998 Q 06/01/18 X A998 Q 06/01/18 W B027 Q 05/21/18 W B027 Q 05/21/18 V C379 Q 10/07/17 V C379 Q 10/07/17 U D032 Q 10/07/17 T E001 Q 03/31/18 T F221 Q 11/01/17 T G693 Q 06/19/18 T The result without the proposed /RETAIN option: v1 v4 v2 v3 A998 Q . A998 06/01/18 A998 . Z A998 . Y A998 . X A998 . W B027 05/21/18 B027 . V C379 10/07/17 C379 . U D032 . T E001 03/31/18 F221 11/01/17 G693 06/19/18     ... View more

It would be useful to have an informat like MDYAMPMw.d but for us non-US users. ... View more

The main limitation with the SAS MD5 hash function (and SHA256) is the 32K data length limit.  This doesn’t allow the creation of a hash for, say, a large file which is consistent with externally MD5 generated hashes, although an internally usable hash is easy enough to generate with chaining.   I am suggesting an extension to the hashing functions that saves the internal state between calls and resumes the hash process with further data.   For example:   * running hash of 'part1', initalise state ; hash = md5('part1',internal_state_id1,'i');   * running hash of 'part1part2' ; hash = md5('part2',internal_state_id1);   * final hash value of 'part1part2part3' ; hash = md5('part3',internal_state_id1); ... View more

PROC FREQ is a core procedure.  It ought to be possible to display MISSING values at the bottom of the output rather than at the top (without creating a NOTSORTED format for every single variable!).   I frequently want to see -- and report -- cumulative frequencies of the non-missing values before seeing the impact of the MISSING values on the distribution of my nominal variables.  It is a big pain-in-the-bottom to not be able to put MISSING values at the bottom.   I am suggesting a BOTTOMMISS option -- or perhaps a NOPAININTHE option -- for the FREQ (and TABULATE) procedures.   Example: PROC FREQ DATA=DATA1 ; TABLE V / MISSING NOPAININTHE ; RUN ;   v1 Freq % CumFreq Cum% CAT1 274,948 19.31% 274,948 19.31% CAT2 6,663 0.47% 281,611 19.78% CAT3 196,687 13.82% 478,298 33.60% CAT4 560,603 39.38% 1,038,901 72.97% CAT5 299,029 21.00% 1,337,930 93.98% Missing 85,753 6.02% 1,423,683 100.00% ... View more

It should be possible for the user to set whether or not we want "Project Log Off" or "Project Log ON" to be the default.  OFF should not be the default unless the user has the ability to change this default setting. ... View more

Hi,   Our datasets are currently stored in Google Big Query.   Access from SAS is done via ODBC Connector (Simba ODBC Connector).   This connector has to be improved by a specific connector, as it is done with Netezza, Oracle and many other DBMS. Indeed, for example, we can not manage to open Big Query dataset via SAS Enterprise Guide interface using click-button. There are other issues which impact the usage of SAS.   Could you take my idea in consideration, il will be very helpful for our 80 users ?   Regards, Gaetan ... View more

I love the fact that we can copy an output node from one EG project to another.  The problem is that EG decides where the copied results node should be placed -- and it is never where I would want it placed in the Process Flow diagram.   We need to be able to "reformat" our Process Flow diagrams so that after developing a process it can be arranged visually the way we wish it to be visually arranged.   It would also be nice if we could instruct EG to not necessarily display lines between nodes that sort a data set and the data set.  It is visually distracting to have several lines from different parts of a Process Flow going to a data set just because it had to be sorted multiple times.   Similarly, it would be nice to be able to instruct EG to not display selected data sets in the Process Flow.  When I need to create several temporary data sets that are just "interim steps" I do not want them stacked up in a column so that the data set I am really interested in is displayed way down in the Process Flow.  One solution would be to simply instruct EG to not display certain output data sets. Another solution would be to allow us to reconfigure the arrangement of output data sets and have that arrangement made "permanent".   As good as Enterprise Guide is as a tool for visually organizing process flows, it still has serious flaws. ... View more

Often in reporting we do the same thing to several variables - print them, calculate statistics, etc.  For example, in the hypothetical store scenario we might sum the number of shipments, the number of returns, the amount of inventory cost.  I propose an enhancement to base SAS to allow definition of a named group of variables  that can then be used everywhere and be expanded into that list of variables.  This would make some programs a lot "cleaner" and save time writing programs. For example DATA My_DATA(KEEP=Store Store_Variables);     SET Input_Dataset;     GROUP Store_Variables Shipments, Returns, Inventory_Cost, Sales; PROC SORT DATA=My_DATA; By Store; PROC MEANS DATA=My_DATA; By Store;       VAR Store_Variables;       OUTPUT OUT=Store_Summary;                      SUM=Store_Variables; Store_Summary should then contain Store Shipments Returns Inventory_Cost Sales  which are sums of the input data variables of those names. For discussion:  should the named group be carried forward if all of its constituent variables exist in the summary? Should PROCs instead support naming groups for output variables?  Should GROUP be a dataset option instead of a DATA step statement? ... View more

"resetline;" as a statement in my sas program re-starts the logfile's line numbering scheme to 1.  The problem occurs because I want to reference errors in my code when I have embedded include statements (which add lines to the log) that offset the numbering.  I want to be able to reference my sas file to correct changes using the line number produced by the log above the error.  I could write in my sas program, say:  "resetline 17;" (if the line after the include statement is the 17th line) This would allow me to reference the exact line of code that matches what the log file says.   Example :  sas file: {many lines of code} . %include file1; %include file2;   log's line number is now offset by the number of lines in file1 and 2.   ... View more

I wish that the datasets in the "Output Data" tab can be sorted by the datasets' name.   For example, my SAS codes created 35 datasets which are shown in the "Output Data" tab, but they are not sorted by name, therefore it is difficult to find the dataset I want to check. ... View more

During the recent delivery of the SAS Visual Analytics 8.3: Basics course, I did a demo highlighting how Data Views can now be used to provide a "business layer" between the CAS Table and the Report, which would be used as the basis for future reports.   The functionality is great but, as far as I can tell, the only way to determine if there is a view associated with a CAS Table is to add the data source to a report, then click Data Options and select "Data View..." from the menu.   Suggestion(s):   Minimum: If there ARE data views, indicate how many in parenthesis beside the Data View... menu option in VA.  e.g.  Data Views (2)...   Better: Suggestion above, and change the behavior of the menu so that the Data View... option is disabled if there are NO data views associated with a selected data source (similar to how the Data Source Filter only shows Edit/Delete Data Source Filter options if there are data source filters currently in effect.   Ideal: Both of the above techniques, plus an indication in the Manage Data application and the Add Data Source dialog box within VA, which allows expanding the Available list for tables with Views, to see the views.  If clicked, the Details shows the structure of the view (Sample Data and Profile would disappear).         ... View more

The %margins macro from SAS is very useful, but it requires SAS/IML. Can the macro be revised to not require SAS/IML?   http://support.sas.com/kb/22/604.html   (Posted by suggestion of SAS: https://twitter.com/SAS_Cares/status/1122944288999059458)   Thank you! ... View more

Often times I use the WHERE button in the dataview which works great. It would be very helpful to be able to quickly sort the dataview either in the normal view or while using the WHERE button. This would make validating data much faster than having to create a new query. ... View more