Version SAS Viya 2025.03 LTS   Issue When there are a multitude of nodes present within the current schematic-style layout of the SAS Lineage tool - to the point that they don't even fit in the "Overview Window" - this presents a rather non-User friendly display of content to the Platform Admin.  Plenty of scrolling and clicking is involved in order to retrieve data on each node object -     Feature Request For usability, please can a "List View" be developed to provide easy + rapid consumption of Lineage content for the Platform Admin?   Example -     Additionally, please can a "Download" button be added? We would also be very happy if there was an option to update a cas table, such that this content could be viewed through a VA report. These 2 items (List View + Download button) could be added to the "View Settings" pane with Lineage -   ... View more

Hello everyone,   at the moment it is not possible to use libname options (for example BULKUNLOAD ) for the Postgres engine in SAS 9.4. This is a major issue for the effective use of Postgres in a SAS 9.4environment. Enhancing the interface would be very helpful in enabling Postgres to be used in a way similar to DB2. Otherwise, we are missing the integration of a widely used Database Management System.   Thanks in advance.     ... View more

I would like to request a feature where there is a sound notification when the code finishes running. Currently, if there is code that takes a long time to run, it would be nice when I switch to another task to be notified by a sound that the code finished running. Possibly there can be different sounds for when there is an error, warning, or successful run. ... View more

Hi Team,   We understand from SAS release roadmap that SAS Drive will be decommissioned after December 2025.   We request the incorporation of a new feature or tab within the Explore and Visualize page to replicate the functionality of the former Reports tab in SAS Drive. This tab was essential to our end users' workflows, as it provided a centralized, flat list of all reports accessible to the user, eliminating the need to manually browse through multiple folder levels. The current Explore & Visualize interface does not offer a comparable experience, making it less efficient for users who frequently access a wide variety of reports. We kindly request that a dedicated section or tab be added to Explore and Visualize, offering: A flat, searchable list of all accessible reports Functionality to pin or favorite commonly used reports A user-friendly replacement for the navigation experience provided by the SAS Drive Reports tab   Thank you for your support. ... View more

I'd like to propose a necessary improvement to the user experience when fitting Generalized Estimating Equations (GEE) models in SAS procedures like PROC GENMOD or PROC GEE .   The Current Problem   When fitting a GEE model, Likelihood Ratio Confidence Intervals (LRCI) are fundamentally unavailable because the GEE approach only specifies a mean-variance relationship and not a full likelihood function.   Currently, if a user specifies the LRCI option in the MODEL statement for a GEE, SAS simply ignores the option without any notification. No warning or note is printed to the SAS log. No message is added to the results output.   This silent behavior can mislead users into assuming the intervals were calculated or even that their model setup might be wrong, wasting time and potentially leading to misinterpretation.   The Proposed Improvement   SAS should implement explicit and multiple notifications when the LRCI option is requested for a GEE model:   1. Immediate Log Warning (Highest Priority)   A clear WARNING should be issued to the SAS log explaining the technical reason the option is ignored. Suggested Log Message: WARNING: The LRCI (Likelihood Ratio Confidence Interval) option has been requested but is not supported for models fit using Generalized Estimating Equations (GEE). This is because GEE does not specify a full likelihood function. The option will be ignored, and default Wald confidence intervals will be reported.   2. Note in the Results Output   A brief note should be added to the output table (e.g., near the Parameter Estimates table) to confirm what was actually calculated. Suggested Note in Results: Note: Likelihood Ratio Confidence Intervals (LRCI) were requested but could not be computed for this GEE model. Default Wald confidence intervals are reported.   Why This Matters   This is a critical usability improvement. GEE is a common and powerful method, and providing clear, instantaneous feedback prevents confusion, saves user time, and ensures that new or experienced users fully understand the inferential methods being used in their analysis. ... View more

SAS VIYA Workbench should be available on-prem and it should ideally be an integral part of the SAS Viya platform. ... View more

Hello team, When attempting to export our SAS Visual Analytics report to PDF, we see: “This report has no printable content.” Our affected pages rely primarily on Data-Driven Content (DDC) objects. Please enable PDF export for the report and ensure sections containing Data-Driven Content can be exported. If native PDF rendering of DDC is not supported in our version/configuration, could we implement one of the following so stakeholders still get governed PDFs? Provide a printable fallback (e.g., mirrored KPI/table/chart in a print-friendly section). Allow the DDC app to expose a static image endpoint so VA can place a printable snapshot. Use a controlled image placeholder (updated on refresh) that represents the DDC state at export time. ... View more

SAS Studio have "Server Files and Folders" that allows to Drag & Drop files and folders. While it can be convenient, it can be source of accidental file or folder shifts.  There can be examples of folders (e.g., because they were close in favorites) silently moved into distant folder without user noticing it and then it can be very hard to find who moved file, where or when it was moved. Please add option(s) (below listed by preference how to risk mitigate) to: 1) add confirmation dialog for drag and drop (it exists in WinSCP and aimed to minimize similar incidents) 2) turn off drag and drop functionality   ... View more

Is it forseen to work with SAS notebooks in SAS Studio (just like Jupyter Notebooks) via a web bowser? ... View more

In VA I have a line chart over time (x-axis) that displays the results of different KPIs (y-axis) according to a selection in a listbox. All KPIs have "Value" and "Average" and some have a "Target value". If I add the three roles, then I get a legend item for Target value even if the currently shown KPI doesn't have one (it's missing in the data). Preferably one would like to choose to display or not display the legend item when data is missing. Second best would (in my opinion) be to never display the legend item for missing data.  This would, again in my opinion, be needed for all chart objects.   Regards   Andreas ... View more

Certain VA reports can be very generall with lots of possibillities of filtering. A user of such report may want to be able to save a selection of filters as a bookmark and not have to manually add the filters each time the user visit the report. Instead the user can just apply the saved bookmark and gets the desired filtered values. ... View more

I became a big fan od SAS Studio recently. But there is still one feature in SAS EG that is still winning me over, but I wish this would also be available is SAS Studio: Auto-completion for variable! While auto-completion for libraries, dataset and SAS sytnax in gerneral just works as fine in SAS Studio as in SAS EG, I don't understand why the auto-completion is not available for data fields/variables from a dataset (as it is in SAS EG)? ... View more

Our users are often not very impressed with the reports me and my colleagues make for them. The reason is that they only see the first tab of the report. The tabs are so subtile that the users don't even see them. It's also hard to see which tab is selected. Please make it possible to style the tabs so that we can make them "pop" more.   Picture to show what I mean: Picture of "invisible" tabs in a VA report     ... View more

Current situation: An established pattern in SAS Enterprise Miner is to use the IGN-node with binary transformation of a linear target variable to go on and make use of the scorecard node to make a logistic regression model based on the binary transformed new target variable. In Model Studio this pattern is only partly implemented as it is only the binary transformation in the IGN node that is possible to use. Due to the current limitation of Model Studio that prevents the user to switch target variable within a project, it is impossible to add a scorecard node to the IGN node as the project is initiated with a linear target variable. This behavior is confirmed in support case CS0221275.    The result is that the user has to make use of multiple Model Studio projects to be able to build a LGD model as proposed in this paper 141-2012: Building WOE Binned LGD Scorecards using SAS® Enterprise Miner™. In addition, if the user wants to build a scorecard model as a challenger model to other kinds of LGD models that make use of a linear target you end up with a scattered process with models developed here and there.   Desired outcome: Make it possible to create a scorecard model within the same project as where the binary transformation is performed.    Added benefit: Easier to document the model development and easier to maintain the model development project (mind you that these models and highly regulated and tend to live for years ). Easier to utilise link to Model Manager from Model Studio. When pushing a model from Model Studio to Model Manager, the default behavior is to create a new Model Manager project pr Model Studio project and this would then possibly result in multiple Model Manager projects if not resolved.    Negative effect of change: None.   ... View more

I know this has been suggested before, but the issue was closed. (https://communities.sas.com/t5/SAS-Visual-Analytics/Mouse-wheel-graph-interaction/td-p/435358) We are about to publish reports for a big number of users with low computer experience. Using VA is a very small part of their daily job. To educate them all on how to avoid unintended zooming in graph objects, is not a feasible task. A possibility to deactivate mouse wheel zoom would be a great increase in usability for our VA reports, and massively reduce our support burden. I really hope you can consider implementing this soon. Thanks in advance. ... View more

Is it possible to atomatically save sas code while working in SAS Studion from the web browser? ... View more

I miss the possibillity to build a general table that can be tweaked by the report user. There are no problems filtering in a table but i dont find any good way to add or remove varibles from a table. One user might want to have it grouped by gender, another by location and a third by gender and location. Same with measures, someone might just want to see the sales while another want sales and cost.  My thinking is something like an object, where i as a report builder, associate the potential variables to the object but it is up to the user of the report to decide which to use and in what order. More or less like a Pivot table in Excel. ... View more

In SAS Viya 3.5, Visual Analytics includes a Just-in-Time (JIT) load functionality designed to refresh data/code every 5 minutes. However, this frequent refresh negatively impacts our database due to the continuous load. Is it possible to implement JIT load as a parameter setting in VA? This would enable reports to filter whether JIT should be enabled (Yes/No). This flexibility would allow smaller queries to benefit from JIT while larger tables and reports could disable this feature to reduce the database load. ... View more

I have a bunch of SAS files in a directory, that I'm running using sas-viya at the command-line with. Here's the command line I use:   sas-viya batch jobs submit-pgm --context default --wait-results --pgm basic_digits.sas   I have two product suggestions that would reduce some friction:   First, I end up with a bunch of JOB folders with undistinguished names. For example here are three in the folder right now: JOB_20240510_011340_087_1 JOB_20240514_201600_284_1 JOB_20240514_202431_319_1   Without going inside of them... which of those was used to run basic_digits.sas, which was used to run advanced_digits.sas, and which was something else?   I would like to be able to provide a parameter to sas-viya that adds something after the JOB_ , and a way to default to having the name of the SAS program there. I would like something like "--results-dir-prefix" that would create this: JOB_basic_digits_20240510_011340_087_1   I *could* create one "output_{}" folder for each file and use "output_basic_digits" with --dir flag, but I wish for something where I don't have to modify the command line in two places for each job with different filenames [high susceptibility to human error]. You could also use the job name from --job-name, but that still suffers the "two command line edits" problem.   Second, "--context default" shouldn't be necessary. If one doesn't provide the context, it should use the default.   Thank you, Gary ... View more