We license the Field Quality Analytics solution and we routinely experience users that don't know the difference between unadjusted, adjusted, and extrapolated, especially when combined with minimum/maximum exposure, and the minimum sample size parameters.  This leads to different users doing things differently, sometimes unknowingly.  This presents problems when communicating the data with others, because the settings can drive very different results and cause confusion.   I'd like the ability to control at an individual user level what capabilities they are allowed/not allowed to leverage within FQA. For example: If I don't want a set of users able to use FQA's "extrapolation" or "adjusted" methods, then I want to be able to put them in a security group that provides them with the full suite of FQA, but only allows them to run an unadjusted analysis.     This request is for more than just that field, it would be nice to have all of this dynamically adjustable per our needs.  This would allow us to control what users can do in the software more until they meet certain milestones or criteria that gives us confidence they know how to use the software with the additional settings. ... View more

In EG 7.x, when a project was run, the results were automatically displayed.  In EG 8.x, this feature was turned off.  SAS Technical Support indicated this was design feature to improve performance.  Although, this would be nice to be able to be controlled by the preferences.  Many of our users kick off their projects to run and are not necessarily monitoring it or have the 'Submission Status' displayed, so there isn't any visual indication that the project actually ran.  In the past, they used the displayed results as this indication.   The idea is to allow the user to set in their preferences whether or not to display the results within a project.  Currently, they don't have this option and they are not happy this functionality was removed in 8.x. ... View more

The "Submission Status" within SAS Enterprise Guide and SAS Studio in SAS 9.4 always puts the most recent entry at the end of the list.  However, if numerous jobs have been run, there may be scrolling needed to view the last entry.     The suggestion is to either have the list in date descending order even better, have list sort-able by any of the fields. ... 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

If the update host-name references option in SAS Deployment Manager can show following information it would be really helpful.   1) Count of files that will be updated. There could be a large number of log, perf log files which aren't required during this change. An estimate of the number of files can help to better plan and remove any unwanted files in advance.   2) Estimated time of completion. In-case of multi-tier large SAS deployments it could take some time for the process to complete. One way to check if the process is running fine is to verify the log. If the system can display a progress bar with the percentage complete & remaining it would be helpful. Currently it only shows which component it is updating but there is no progress in terms of percentage displayed. ... View more

Provide shortcut keys for Close, Move Up, Move Down, Properties , and tab grouping commands in the drop down box for items in the Open Items list.   ... View more

That will be great to have a tool like a Todo list implemented in SAS enterprise guide for each SAS project. In fact, I do not think I am the only one who has to write a program on many days. That will be great to have a Todo list in order to organize what is left to be coded... and what is already done. for each SAS project;   ... View more

SAS Institute-supplied functions allow optional parameters:   A=substr(B,2); It would be very useful that custom-built functions have the same ability.   ... View more

Can you add something like, if we add ? before the function, it opens the help doc in result viewer. The help doc should give brief description of what the function is, what are the required arguments and optional arguments and brief description of arguments. For example, If i write ?strip(), it will open the document with description of what strip does and all required and optional arguments. This can be done for procedures too, For example, ?proc import, this gives brief description of proc import, required/optional arguments/options. I have seen something like this in R-studio. ... View more

Functionality should be added to PROC REPORT to allow sorting for summarized rows. This would avoid pre-processing steps prior to execution. ... View more

At the moment, this data T; A1='2:30:00 pm'; A2=input(A1,time11.); A3=input(A1,anydttme11.); B1='2:30:0 p.m.'; B2=input(B1,time11.); B3=input(B1,anydttme11.); run; yields A1 A2 A3 B1 B2 B3 2:30:00 pm 52200 52200 2:30:0 p.m. . .   ... View more

The purpose of CATXF would be to concatenate formatted values with a delimiter. CATXF(format, delimiter, item-1 <, ... item-n>) If format is not present use the variables format attribute. A null delimiter would be a null delimiter (not an implicit 1-space)   Example: array items (5) _temporary_ (1:5); result = catxf(z4., '', of items(*)); Result 00010002000300040005 ... View more

Provide drag and drop actions to help order the Open Items tab.   ... View more

One of the convenient SAS features I enjoy is the #byval feature in procedures such as proc gplot, proc report, etc. without resorting to macros. the obvious limitation is that it only works for one proc at a time, so if I want to run a series of procedures one by-group at a time (e.g., proc odstext followed by proc report for the first by-group, repeat for the second, etc.), I cannot do that without resorting to macros.   Would it make sense to create a new procedure such as proc encapsulate that would enable the user to have more control over procedures? An example of a rough sketch would be (example modified to make it more clear that all datasets involve require common primary level masterby variables).    proc encapsulate;    masterby MASTERVAR1;    proc odstext data=input_data "This is the report section for #masterbyval1"; quit;      within MASTERVAR1 do over MASTERVAR2;        Title "Text for #masterbyvar(MASTERVAR1) #masterbyvar(MASTERVAR2)";         proc report data=input_data2;         run;     endcomp; run; ... View more

Can the following be implemented? : A colon preceding a suffix selects with variables with the common suffix, as would select variables AC and BC in the second data step below, without error: data have; AC=1; AD=2; BC=3; BD=4; AEC=5; BED=6; data _Null_; set have; format A: z4.; putlog _All_; data _Null_; set have; format :C z4.; putlog _All_; run; Colons sandwiching a search term as a use of colon wildcards, as in:  format :E:  z5.;     Also see sasnrd.com = Drop or Keep Variables With Same Suffix ... View more

Hi, SAS developers, I checked whether this issue has been reported or not but did not find the related posts. Check the following SAS log ran with SAS 9.4: PROC SQL used much more time than PROC SORT on the same data. It seems that PROC SQL did not use the threading and parallel CPU power when counting distinct rows. Hope this can be improved with PROC SQL. Thanks!   82 proc sql noprint; 83 select count(unique(Pat_ID)) into : Count_1 from UnsortExtraVar; 84 %put Count_1=&Count_1; Count_1=38879956 85 quit; NOTE: PROCEDURE SQL used (Total process time): real time 6:37.73 cpu time 6:37.78 86 87 88 proc sort data= UnsortExtraVar out=SortedExtraVar nodupkey; 89 by Pat_ID; 90 run; NOTE: There were 440979767 observations read from the data set WORK.UNSORTEXTRAVAR. NOTE: 402099811 observations with duplicate key values were deleted. NOTE: The data set WORK.SORTEDEXTRAVAR has 38879956 observations and 8 variables. NOTE: PROCEDURE SORT used (Total process time): real time 2:11.29 cpu time 4:38.69 91 proc sql noprint; 92 select count(unique(Pat_ID)) into : Count_2 from SortedExtraVar; 93 %put Count_2=&Count_2; Count_2=38879956 94 quit; NOTE: PROCEDURE SQL used (Total process time): real time 55.10 seconds cpu time 55.11 seconds ... View more

Please improve the diagnostics when reading malformed XML via SAS XMLMAP.   When there is an error, the error message in SASLOG is poor, only giving a general description of the error without giving any specific details.  For example, the element or attribute name is missing, so it's hard to locate in the XML file (see below).   It might be ok if the line number actually showed the line number, but instead SAS treats the entire file as a single record, and we have to figure out where column 150166 is.  This is z/OS, and there are no new-line characters, so the XML engine must rely on the count of reads to know how many records were read.    The problem is especially bad as we often use variable length records.  We have no way to know which record has the error.  This is fundamental in z/OS, but this SAS XML engine must not be aware of z/OS files.  Please fix this.     ERROR: The attribute name is duplicated in element definition.        occurred at or near line 1, column 150166     We also want the ability to detect the error in our SAS code so that we can handle the error ourselves.  Placing the error in the SASLOG doesn't help the person that submitted the XML since they are not the ones running the SAS job.  Instead another team runs the SAS program.  What I would like is the ability to detect the error in the SAS code so that I can send the error to the team that writes the XML via an email.  For example, have an option on the LIBNAME or OPTIONS statement that specifies a SAS dataset name to contains the errors.  The fields could be "Line, Column, ErrorMessage, Severity, Element, Attribute".  Then if there is an error, a subsequent DATA statement can read the file and build a report, so that the error messages are not squirreled away in the SASLOG.    One more source of problems is when element or attribute names are mistyped.   If an element or attribute is optional and is misnamed, we have no way to detect the error.  For example, <MyElement name="Element-1" count="1">, if count="1" was entered as uppercase COUNT="1", it would not match the map and so not be read.  If the default of count is 0, we would not know that they really wanted 1.  The solution would be to throw an error whenever unknown elements or attributes are found to the error file above.  Then a subsequent step could read the errors and decide what to do.    Thank you, Michael Giaquinto VP, Principal Engineer Wells Fargo       ... View more

SAS should include an IDENTITY column attribute to provide compatibility with other database systems.  In my use case I would like to develop code that is 100% compatible between DB2 and SAS by simply modifying the LIBNAME statement.  I can simulate IDENTITY column functionality by generating my own value, but that would not work for code that has already been developed for another database like DB2.  I would need to know that I am in either a DB2 or SAS database environment and then have different code paths.  Or eliminate the use of the DB2 IDENTITY column and always generate a number.  Both choices are not feasible at the moment.   Per Wikipedia: "An identity column is a column (also known as a field) in a database table that is made up of values generated by the database. This is much like an AutoNumber field in Microsoft Access or a sequence in Oracle. Because the concept is so important in database science, many RDBMS systems implement some type of generated key, although each has its own terminology" ... 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