Changing the permission of a local copy of a repository file results in unnecessary unstaged changes in GIT UI in SAS Viya 4 Below property needs to be added in SAS Viya GIT configuration to avoid this, but its not possible to do so yet. git config core.filemode false     ... View more

I can't imagine this would be a very difficult thing to add. It would be easier on the eyes for those who prefer dark mode for their other devices. Also it would benefit those of us who code late at night and don't want to be blinded by a white screen. R*Studio has this mode built in. I think SAS Ondemand/Studio would benefit greatly from it's inclusion! ... View more

I would like to suggest a feature for SAS Enterprise Guide that allows users to perform a global "Find and Replace" across all open programs at once.   Currently, the Find (Ctrl+F) and Replace (Ctrl+H) functions only work within a single program window. However, when working with multiple programs simultaneously, having an option to search and replace text across all open programs would greatly enhance efficiency and productivity.   Suggested Features: A new "Find and Replace in All Open Programs" option. The ability to preview and confirm changes before applying them. Support for regular expressions (optional but useful). This feature is available in many modern IDEs and would be a valuable enhancement to SAS Enterprise Guide.   Thank you for considering this suggestion!   P.S. My current version is SAS Enterprise Guide 9.4. ... View more

The program editor in Studio under Analytics Pro is missing key features that are present in 9.4. This request is to add two features in the "Open" window, as follows: 1.  display file size, file type, and date modified. Allow sorting on any of these fields by clicking at the top of the respective column. 2.  display the last X files that were opened. The number of displayed files should be configurable, and double-clicking on a file name should open it. ... View more

We found out, that using special characters or national characters like äöü cause problems when they are in the passwort of a user and saved in an authdomain credentials. Libnames then do not have access to the credentials any more resulting in a Warning in the log and failing libnames.    I suggest, that sas automatically pwencodes the passwort before saving it to the authdomain or at least builds a toggle to pwencode it optionally so that every password can be plain inputted in the field and saved in a way that it works in libnames.  ... View more

Hi. According to SAS Support, it is not possible to have Minio tool without SAS Viya. Is it possible to develop and provide us a Minio library, suitable with our SAS version 9.7M7? Thanks for your return. Regards. ... View more

Change default behaviors to "automatically overwrite" if that's what most users want, but some of us got a lot of use out of this option. ... View more

Provide a SAS Studio Step (or Custom Step on git) to allow for parallel processing of sub flows (similar functionality to DIS Fork transformation).  Such a step should allow to address requirements as raised in forum discussion Launch asynchronous SAS program within SAS Studio in Viya4 @MMar @JuanS_OCS  ... View more

Working on multiple concurrent studies in SAS Studio (using v3.8) causes a risk of confusion as each repository is shown using only the directory name of the local repository.  In our example this is always the name "programs" as part of a standard folder structure, no matter the client or study. When registering a Git Repository in SAS Studio or Enterprise Guide, it would be valuable to have an additional input field for a user to specify a friendly name or label to be shown in the client application. The friendly name would be shown instead of the directory name when one is provided.  I have attached a mock-up showing the issue and a UI screen of my envisaged solution. ... View more

SAS Studio currently (Viya 2024.08) uses the same icon for SAS Program nodes in flows regardless whether it is embedded code or referenced external file. Looking at a flow, there is no way to distinguish between those two types. If you want to know, you need to click on every single node and look to Code or Node tabs. It would be very beneficial SAS Studio can use different icons for SAS Program nodes based on whether it is embedded code or referenced external file. The same holds for Python Program node. I believe it takes just a little effort with the great impact on usability.    Here are just two examples: 1. Embedded code (as there is no path shown at the top of Code tab) Embedded code 2. Code referenced externally (the path to the external file is shown at the top of Code tab) Code referenced externally   ... View more

According to this usage note, there's an old defect for CONNECT USING together with OLEDB access: 48877 - A pass-through connection invokes the Data Link Properties dialog box even though an assigned OLEDB libref is also present (sas.com) CONNECT USING was imoplemnted because it's conventient to avoid keeping connection information in many places. Also, this especially nice when you want to generete the connections dynamically in PROC SQL. ... View more

SAS Mirror Manager can upload/push SAS images to some container registries like AWS ECR. I suggest to add an option to allow to delete/remove SAS images in order to be able to cleanup the container registry. For example, if I use SAS Mirror Manager to upload three SAS releases to AWS ECR: Stable 2024.04, 2024.05 and 2024.06. Now I want to delete all SAS images that belong to release Stable 2024.04 to cleanup my AWS ECR but there is no option in SAS Mirror Manager to do it. ... View more

Prometheus currently only tracks active jobs, with no visibility into completed ones. Once jobs finish, their status information from the Workload Orchestrator is not available to prometheus, limiting post-completion monitoring and analysis. It would be beneficial to externalize this data to Prometheus for better job status tracking.  ... View more

I discovered in my latest tech support track: CS0136992 that client IP Address is only passed to the metadata logs for calls related to: New Client Connections  Redirects for the client in the cluster  AND - it cannot be configured to be added for other logging events! SAS Help Center: X Conversion Character I would like to request the ability to add Client IP Address as a descriptive characteristic to various Metadata Audit logging events such as:  Group/Role Changes Logon/Logoff Role Permissions Changes  Client IT teams often work with Splunk & other tools that query logs using a NoSQL query language. As duplicative as it may be - this allows IT teams to easily comply with security and tracking requirements to be able to easily track and identify cyber security events and get all information in a single query.    Without this - what I'm being told, is security teams would first need to identify the event in question, then using the request ID - track that all throughout the logs until they found the initial new client connection in order to find the source IP. This kind of sub-query is incredibly tedious behavior and creates a significant disconnect that must be manually traversed in order to create the wholistic picture cyber security teams are looking for.    Please include this as a feature in the next release!  ... View more

Expand the DNUM and DREAD functions with an additional "modifier" parameter, so hidden files (where the name starts with a dot) are included in the count and can be found.   Such files can be listed by using the -a parameter of the ls command, so their "hidden" status is relative, and the additional parameter of the functions would avoid the need to use external commands (which, in turn, forces SAS admins to enable XCMD). ... View more

PRX-functions (prxmatch(), prxparse(), etc) that deals with regular expressions still cannot process multi-byte character sets like UTF-8 in the SAS 9.4 releases. It is an essential feature that would facilitate a lot a migration to a MBCS context. ... View more

Starting with SAS Viya version Stable 2024.05, PROC PRINT will now display an empty table in the Results window if the source data set has 0 rows. This is a change from previous versions going back to SAS 9. Prior to this change, running PROC PRINT from a data set with 0 rows sent no output to the Results window.   Some users generate "check" data sets in their code that create rows of data and display results only if something unexpected has happened. This recent change in SAS Viya 2024.05 now causes "false alarms" to go off in previously stable code, as results are now generated from empty data sets.   Although this new behavior can be avoided by adding extra code to check the number of rows in the data set prior to running PROC PRINT, end-users' code would be less impacted if an option was added to allow the user to decide if results should or should not be generated when the source data set has 0 rows. Please consider adding such an option. Thanks! ... View more

In large enterprise organizations, it would be beneficial to be able to hide, or make visible, folders from the SAS server files that are mounted from the Studio Explorer pane based on the groups the users are in.   See Case: CS0115567 for the original support question and example. ... View more

There have been quite a few spam questions over the past few months where it took sometimes days until they got removed.   Proposal Implement an automated process that moves questions from the visible list to some hidden queue for investigation if marked by multiple users an inappropriate content.  To avoid that this process can get misused: Only include users that marked the question if they are not New Users but already on a certain level (to exclude fake users).   And just thinking: Eventually request from New Users for their first few post some additional identification step when posting a question to make it a bit harder to automate posting such questions. ... View more