Hello,   Mirroring the WORKPERMS system option, valid for SAS UNIX/LINUX    https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/hostunx/p1bd28x2b4hcwin1b68clthsekf8.htm   A new system option - let's call it USERPERMS , would be very useful to harden within SAS the security of the SASUSER directory path the first time it is created.   syntax :   USERPERMS < POSIX security profile 700, 775, 750 etc.>   ex. -USERPERMS 750  creates the directory with the following permssion profile drwxr-x---. 2 userid group 4096 Apr 21 14:34 sasuser.v94   Valid in configuration files   The workarounds exist, of course, but they entail the execution of sensitive system commands like chmod in an automated script, which is not a good practice in my experience. Permission assignments should never be run automatically, thats a SPOF large enough to make way for uninvited accesses when the automation itself malfunctions . Instead, use umask initial value setting like ... WORKPERMS , or soon USERPERMS ?    Comments are welcome,   Best Regards,   Ronan   PS. Sorry if this request duplicates another , I was unable to find a previous one. ... View more

Hi everyone,   at this moment, SAS VA (SAS Viya 3.5) defaults to redirect a user, when is closing a report, towards "Visualize and Explore". Which is fine but also a little bit strange for a user in 2 main aspects:   The "Share and Collaborate" view (aka SAS Drive) shows a list of the reports available, very natural for a user, as it also shows the favorite and recent reports. When a user logs in, it is by default redirected to the "Share and Collaborate" (SAS Drive) view, which is very good idea, however they are not redirected to it when closing a report. Therefore losing some coherence and forcing a user to find the "Share and Collaborate" to back to initial landing page and find a report. If anyone is interested, this has been discussed with SAS Technical Support in the ticket 7613324421, and the answer was that this is not available at the moment: nor by publicly documented and supported methods, nor by unsupported/undocumented methods, as it is sometimes the case for some Java and application variables.   The request would be to allow the customization of this kind or redirection. For starters, for the event of closing a report and decide that the landing page will be the same as when a user logs in. Further and wider options would be also appreciated and a good idea, although not the main point of this request.   Would it be possible? Any thoughts? Would love to hear from you. Thanks in advance for the consideration!   Best regards, Juan ... View more

Currently in SAS 9.4M7 it is possible to show the values of the x, y and response variable in the tooltip. These may be selected and formatted by "roles". In HEATMAPPARM one coloured rectangle represents one data row, so it would be possible to show the value of any variable in the dataset in the tooltip, e.g. some kind of unique identifier. This would be useful. Please add it. ... View more

Right now, trying to use Studio (on Demand for Academics) from my Android tablet with Chrome is an exercise in advanced Masochism. After just a few edits, the code displayed on the screen does not match the code that is actually stored and sent for execution, which is later revealed in the log by ERRORs. The only reliable method to use it right now is: prepare the code in an external editor start a pristine session copy paste the code once submit Please make Studio work on those platforms (copy/paste, edit functions). ... View more

As can be seen here, the default keyboard shortcut layout often interferes with the functions of the client's keyboard, depending on operating system and locale. It would be of great advantage to make the shortcuts in SAS Studio configurable, so that users can adapt them to their local specifics and their individual preferences. ... View more

Hello SAS community, I am currently working on a SAS VA dashboard and in this dashboard I make use of a stacking container. I have some tabs with content created and now I want to make it possible to jump to the first tab again, instead of clicking back to the first tab. Is there a possibillity to do this? Or can this only be achieved by selecting 'restore to default report state'? Hope somebody comes up with a solution... Regards, Arjan ten Cate ... View more

There should be a section added to the settings that lets you direct the Log Summary view (which is already structured basically like a table), to a dataset within a sas library folder, or to external format like excel. It should include options to retain the log output to the window in addition to the external dataset output- you should not have to choose between one output or the other.  Also, it should give you option to limit the output going to the data set to only the content of interest, ie, just Errors,  or Errors and Warnings.   Using Proc Print To just saves all the messy text to a text file.  People need an easy way to send just the Errors for multiple programs to one cumulative TABLE  every day. ... 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 don't know why the INPUT function behaves differently in the DATA step compared to PROC SQL, but it does. I know I can work around it, but I don't think we should need to create a fudge.   I think PROC SQL should be changed to handle the INPUT function in the same way as the DATA step.   The following code hopefully shows what I mean. The expression in the DATA step performs perfectly, but PROC SQL does not like the same expression and throws and ERROR.   **************************************************************; *Create a Numeric Informat. ; **************************************************************; Proc Format Library=WORK; InValue PartNumber 1 =8526961 2,5,18 =6926656 3 =3181908 Other =-9999999 ; Run; **************************************************************; *Create the list of items ordered. ; **************************************************************; Data ORDERS; Input OrderID ItemOrdered ; DATALINES; 555 3 847 1 ; Run; **************************************************************; *Use a DATA step to test out our Informat. ; **************************************************************; Data ORDERS_DATASTEP; Set ORDERS; Part_To_Pick=Input(ItemOrdered, PartNumber.); Run; **************************************************************; *Use PROC SQL to test out our Informat. ; **************************************************************; Proc SQL; Create Table ORDERS_PROCSQL As Select OrderID, ItemOrdered, Input(ItemOrdered, PartNumber.) As Part_To_Pick From ORDERS ; Quit; When the PROC SQL step runs, we get the message: ERROR: INPUT function requires a character argument. To get the expression with the INPUT function to work in PROC SQL it could be coerced into a character value with a nested PUT function, but I think PROC SQL should be amended so that we do not have to do this extra step. Input(Put(ItemOrdered, 12.), PartNumber.) As Part_To_Pick Cheers, Downunder Dave New Zealand         ... View more

Having large SAS 9.4 platforms, a periodic hotfix routine solves a lot of problems in advance. As SAS partner, we support banks and insurance with > 30 SAS servers each. You don't want to do a manual hotfix management with that many servers, so we implemented a mechanism to check for and report new available hotfixes in a compressed format. Therefore, we wrote some sort of HTML-parser (for the HTML files generated by SASHFADD for each server) using regex to gather informations like "is hotfix xyz an Alert hotfix, has it manual steps in it, which SAS product is being hotfixed" and so on. Since this HTML-parsing is quite complex and error-prone, a machine readable file like XML or JSON would be much easier to process. I guess, this is easy to implement, because you already have all the information to do that. Additionally, hotfix dependencies can be listed more easily.   Thanks and best regards!   Chris ... View more

Show timestamps beside existing programs in the open-file-dialog in  SASStudioV (Version 5.2 Viya 03.05). Perhaps also possibility to sort the rows i the dialog in  timestamp-order. Now it's sorted  by name and no timestamp visible..     ... View more

get rid of the table and variable length limitation of 32 characters or bump it up to 128.  This limitation is an annoyance  ... View more

It would save a lot of time if we were able to setup the 16 bar/line colors for a custom graph using custom colors. When swapping the chart into a report or making any changes to it, all 16 custom colors have to be setup again within the report.  ... View more

In SAS 9.4, we were able to create custom queues for each SAS application (EG, EM, FS, SS, etc) and with this, ability to monitor the usage of each application.   However, after much research and trial and error, I'm not finding a way to audit/report on usage of the SAS Viya web applications such as SAS Studio V, SAS Visual Analytics, SAS Data Studio, SAS Environment Manager, etc.   Note: This is this documentation, but I can't get it to work and per SAS, they are indicating it actually doesn't track the web applications since they go through SAS Logon.  (Change Actions and Services That Create an Audit Record)   My suggestion is to have a way to audit/report on user web application usage. ... View more

The OUTFILE= option of PROC EXPORT (and DATAFILE= of PROC IMPORT) allows only physical filenames at the moment. Allowing the use of a file reference (and in particular, the use of filename(member) syntax) would make it easier to export to (or import from) a zip archive with multiple files in it. ... View more

In Output Data window, use "smart" auto column sizing to prevent useless single character object/table names. Especially exasperating when you expand the window to the point where empty white space exists on RHS and still get single character width names....yes, you can adjust the column but surely the default should be more useful than a single character width?   EDIT: btw, adjusting width wouldn't be so painful if it wasn't for the pixel hunting required to do so. This and all other window/tab borders and sub-compartments.... ... View more

My opinion is that there should NOT be new variables created due to missing value imputation. The original variable names are well enough. The process should only impute the new values in place of the missing values for these variables, and NOT create ‘IMP_’- variables,   From analyst point of view, there is no need on having BOTH variables included within your analysis; i.e. imputed and non-imputed values. You always use only one of theses two. ... View more

I would be really surprise if not already suggested based on online searches, but if we have a slider for a date range, we would like to set the range to a default dynamic range.    Example, if the complete date range on the report is the last 90 days, we would like the default view to show the last 30 days, but yet still allow the user to still filter to the previous 60 days if they want. ... View more