Hello,   A lot a usable space is lost on the SAS Logon Manager web page. I find it useful to reuse part of it  in order to display Important/Urgent messages to the incoming users :   for example, maintenance scheduled with outage at < day, time> , system operation scheduled at etc.   I know it's not officially permitted but I have already modified the Logon HTML code , inside the deployed hierarchy of SAS Web App Server to allow this. It worked fine altough the content update process was risky and required editing manually a file on the midtier machine ...   Wouldn't it be nice to allow this kind of feature to SAS 9.4 admins, using an update channel well-devised and somewhat easy to use (for instance, a Stored Process with text fields and some little typographical enrichments to be selected optionally like Red colored text, bold font etc.) ? This would replicate the Message Of The Day (motd) broadcasting feature known for a long time on Unix systems or SAS-wise the (little-known) NEWS system option.   To illustrate my point, I've taken the liberty to take a caption of such a Logon modified page (courtesy of SAS Institute ; )    See picture above.   Thanks for considering this idea !   Ronan   PS I've tagged this idea with SAS Studio even though it's broader actually ... View more

Move "Delete" button on the menu away from the running man button or at least put some space between the two buttons.   I click the running man button to execute a SAS code quite frequently and sometimes click the delete button right next to the running man button by accident, which causes panic! From ergonomic viewpoint, this is a poor design issue.   ... View more

Hi   When you use a precision container to make a long report (longer than 100 %), you are not able to print. Long websites is common today. You can simply scroll down and down, but if you make a report in Visual Analtycs, where you should scroll and scroll, you are not able to print the entire report - all you get is the first page (or all objects in a messy not formatted order if you try to include hidden objects).   For inspiration on long reports, click this link: https://www.sas.com/content/dam/SAS/support/en/sas-global-forum-proceedings/2020/4171-2020.pdf  however, reports are not printable. Please make it printable:) ... View more

At the moment, it is possible to create a single connection to a single LDAP server and in that connection, 2 queries, a single query for users and a single query for the groups.   In the past, the User Bulk loading could allow an array of queries, for both the users and the groups, and also a certain pagination based on number of observations or based on alphanumeric order and you could split the queries.   It would be really nice and useful in SAS Viya, especially in SAS Visual Analytics environments, where it is expected a usage of thousands of users per organisation , the possibilities to:   Create multiple queries, for users and for groups, having different baseDNs and to split internally those queries in additional queries, based on number of observations and/or starting letter (alphanumerical)   ... View more

All the major SAS string handling functions have a macro equivalent: %index %substr %scan %upcase %length   Especially when using %scan, one often has to use %sysfunc(countw()) to initialize a macro loop.   So I propose to create a macro equivalent of countw, namely %countw, similar in function to %scan with regards to delimiters and modifiers. ... 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

Request It should be great to have the possibility to prepare in VA report layout formatting for printing. Currently the solution enable to produce PDF export but feature for formatting layout for printing pdf is really poor also after the last release. It should be useful to have the possibility to prepare report layout in a similar way of what is now available with Sas-guide solution and in SAS web report solution. It’s clear that VA is a solution for report viewer but could be effective to have the possibility to prepare out of VA predefined layout with predefined reports that use the same datamart and objects that user can navigate on line. Let me share a dream: New VA module “VA Reporting”!. The features should enable to prepare report with header and footer with had hoc formatting reusing the same object of current report for web navigation. The component should include the standard functionality already available in SAS web report studio for scheduling report distribution by mail to list of predefined recipients Use case/Workarounds Standard behavior of our user is to publish dashboard on a regular basis (weekly, monthly, quarterly, ..) and the request is very often to prepare a presentation with main figures to be distributed to all relevant responsible eventually with some executive summary comments on figures. Workaround in place so far is the utilization of MSOffice add-in for creating dynamic PPT that retrieve data directly or indirectly  from VA. Consideration   Without an effective feature for report preparation in printable format is still not covered with VA  the “last mile” of BI. Our users  still like and ask static paper base documents that are not  satisfied with SAS suite and this ask futher re-working from user reporting teams with other tools. VA Reporting Module could be an interesting opportunity ... 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

Add some ML to the back end so that when users, especially new users, post SAS code in their posting it is automatically detected and placed in a code block.   No offense, not sure why there is a "Insert SAS Code" and a "Insert Code" feature in the posting editor.  They appear to be the same.  Not sure why some code blocks appear as boxed with white background, slightly oversized font and syntax highlighting. ... View more

This would give us, the longest, shortest, and list of values by group.     proc sql; select longest(STR) , shortest(STR) , list(',', quote(trim(STR))) , listnodup(',', quote(trim(STR))) from TABLE group by ID; quit; ... View more

Please provide option to put the data label inside the stacked bar. ... View more

When switching between the CODE / LOG / RESULTS tabs in SAS Studio, it would be nice when clicking on the CODE tab (with the mouse) to always change the cursor focus to the actual editor window.   Currently after clicking the CODE tab, you need to click down in the editor window in order to start interacting with it.  The problems with this are:   If you forget to click in the editor window and press an arrow key, it changes to a different tab If you click in the editor window, whatever was previously highlighted is deselected If you forget to click in the editor window and start typing, you realize you forgot to click and need to move your hand BACK to your mouse and then back to the keyboard, ugh.     ... View more

Create parameter enabling export cross table with the same design of the original SAS Visual Analytics to Excel. Often users need to edit the data in Excel, while preserving the same design from the SAS.   Thanks. ... View more

We would like to know if it is possible to make the error when trying to log in more specific and indicate the reason why it was not possible. Sometimes the username and password are correct but the real reason for not being able to log in is that the account is locked in the active directory and this is not shown in the application message. Can the error messages be customized to be more specific? For example: Cannot log in because the user does not exist. Cannot login because the password is invalid. Cannot login because the account is locked in the active directory. Cannot login because your password has expired, or your password expires in x days.   ... View more

I would like to be able to display our data in a Radar Chart i VA. http://en.wikipedia.org/wiki/Radar_chart ... View more

When editing the details on an object in SAS Studio we have the ability to add 'notes' it would be nice to be able to use markdown to 'beautify' the notes. ... View more

It seems as though the JSON (JavaScript Object Notation) format is quickly becoming a standard alongside XML with respect to data acquired via web services.  I'd like to see PROC JSON incorporate the ability to read JSON-format datasets in addition to the already-existing write functionality. ... View more

The TERMSTR option is used to define the record delimiter (End of record marker) on flat files. This options does not accept hex values, which is very odd as record delimiters normally aren't standard characters. The syntax   TERMSTR='0c'x   should be supported. The example above was chosen because '0c'x is often used by Hadoop files.   As an aside, this whole option could do with a cleanup as in the following example,   data t; file "%sysfunc(pathname(work))/t.txt" termstr='0c'x; put 'A' / 'B' / 'C' ; run; data _null_; infile "%sysfunc(pathname(work))/t.txt" termstr='0c'; input; putlog _infile_; run; 1- The x is suffix ignored in the first data step's file statement and the delimiter is set to string '0c'.   So the file is 9 bytes long and contains:    A0cB0cC0c   2- In the second data step, SAS somehow finds these 2 nonsensical records:     A0cB   C0cB       ... 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