As a SAS user I would like missing values in a parquet data set to be displayed as a period .   Essentially, we need to implement support for SAS missing values, via Parquet NULL values, within Compute parquet otherwise the, missing may default to 0 or 01JAN1960 which will provide inaccurate reporting. Retain missing for numeric when converting to parquet in compute. ... View more

Currently, when a file is saved in SAS Studio, the Explorer (Navigation) pane is refreshed and automatically returns to the top of the folder tree. I would like an option to disable this behavior and keep the current scroll position and folder focus after saving a file. This would improve usability and efficiency when working with files in deeply nested folders. Thank you. ... View more

What's the rationale for not having a standalone ODS destination? It's pretty common that I only want to export graphic files. It doesn't really make sense that the way to do that is to open up the LISTINGS destination, the destination for producing fixed-width text output. I know that works, but when I step out of my perspective of a long-time SAS programmer, it's just plain weird to do it that way.   Or to put it another way. I regularly teach an undergrad SAS programming class, and utilize the Programming 1 and Programming 2 materials. So this use case isn't directly covered, but I can certainly imagine a student asking "is there a way to just export graphs?" If the WHY question came up, how much would that reinforce to budding statisticians/data scientists any preconceived notions about SAS?    Wouldn't it be nice to have a GRAPHICS or GRAPHICSONLY destination, and maybe have some options that would be handy for that purpose? It's almost crazy to me that this has never been created.  ... View more

Feature Request: Restore Interactive Perspective in SAS Studio Proposal This is a product suggestion to restore the interactive perspective feature in SAS Studio. Background and Functionality For over 40 years, SAS graphical user interfaces (including previous iterations of SAS Studio) have supported an interactive mode for submitting programs. SAS contains dozens of procedures designed to run interactively, including workhorse procedures like PROC SQL, PROC DATASETS, PROC TEMPLATE, and PROC REG. Interactive mode makes SAS operate similar to environments like Python and R: users can submit commands, view results immediately, and execute subsequent commands that build upon the existing state of the program. Further technical details regarding interactive procedures in SAS can be found here: https://blogs.sas.com/content/ iml/2024/10/09/interactive- procedures-sas.html. Impact of Removal The interactive perspective is particularly critical for workflows utilizing PROC IML and PROC OPTMODEL. Without an interactive mode, the process of debugging programs becomes significantly more difficult. Additionally, it forces users to entirely resubmit long-running computational processes from the beginning rather than continuing them sequentially. Current Status The interactive perspective was removed in the SAS Studio 2025.06 (June) stable release. According to the release documentation (https://communities.sas.com/ t5/SAS-Communities-Library/ Faster-Smarter-More-Intuitive- SAS-Studio-2025-06-Stable- Release/ta-p/970842), the feature will not be reinstated unless there is "sufficient demand for this functionality from our customers." This request serves to initiate that demand. ... View more

Would like to see an option in Enterprise Guide that will audibly notify you when a SAS program or project completes.  This would be especially helpful for longer-running jobs when you are working in a different window than where the job is running.  I know that sending an email notification to Outlook can presently accomplish this, but a native option in EG would avoid cluttering up your inbox. ... View more

Hello,   There is no warning in Visual Analytics (on Viya 4) that the SAS license is going to expire soon.   I think that is very important to allow users to be aware as much as possible of this imminent issue (let say couple of weeks before the expiration date) since not always the email with the updated license is received (for example the recipient that is listed on SAS systems left the organization) or is simply missed.   To reduce the UX impact you can show the warning dialog no more than once a day per user or giving the warning in some other way e.g. adding a message in red to the banner or something similar. ... View more

It would improve usability if administrators were able to delete comments. This could be useful, for example, in cases where a comment contains sensitive information. We are using Visual Investigator 2025/09, Release: 20251209.1765255106922. ... View more

SAS Viya Copilot shows that an embedded LLM chat interface helps productivity inside SAS tools: code generation, explanation, natural language Q&A, and so on. Right now that's only available to SAS Viya 4+ customers, and it's tied to one fixed backend (Microsoft Azure AI Foundry). Many SAS users, especially in regulated industries like pharma, will stay on SAS 9.4 Foundation for years. They have no equivalent native option.   I'd like to propose a chat pane for SAS Studio and/or Enterprise Guide on 9.4 Foundation, similar to Viya Copilot's code assistant. The key difference: the LLM call should be a documented macro hook that users can override, not a fixed vendor backend. This lets organizations point the chat pane at whatever provider their data governance allows: OpenAI, Anthropic,  or a self-hosted model.   Why this is feasible SAS programmers already build this by hand using PROC HTTP and the JSON libname engine to call LLM APIs from SAS 9.4, parsing each provider's JSON response and using the macro language to build prompts dynamically. See "Getting a Prompt Response Using ChatGPT and SAS" (PHUSE EU Connect 2024) (proceedings:) and the related SAS Ask the Expert session, "How Can the SAS Macro Language Enhance LLM Integration in SAS 9.4 for Clinical Programming?" (How Can the SAS Macro Language Enhance LLM Integration in SAS® 9.4 for... - SAS Support Communities) This proves the integration works against SAS 9.4. It just isn't native. SAS already has a precedent for macro-driven, interactive dialogue with a user: %WINDOW and %DISPLAY in the classic Display Manager System. A window pauses execution, takes input, and resumes. They're limited to classic windowing mode and don't render in EG or Studio, but they show the underlying idea (macro code driving back and forth with a user) is already part of SAS's own toolkit. A modern equivalent, a persistent chat pane in SAS Studio and EG, would bring that same idea to the interfaces 9.4 users actually work in. Proposed capability A chat pane in SAS Studio / Enterprise Guide, similar in placement to Viya Copilot's code pane. A documented macro or API hook so the LLM call itself (endpoint, auth, payload, response parsing) is supplied by the customer, not hardcoded to one vendor. Conversation state kept across turns in a session, so follow-up questions keep context. Ability to insert LLM-suggested code straight into the active editor, like Viya Copilot does. SAS already has a way to keep credentials out of the log: PROC PWENCODE. Right now, anyone wiring up an LLM API call by hand has to manage the API key carefully or risk it showing up in plain text in the log or saved code. A native chat pane should use the same encoding approach by default, so this is a known, solved problem within SAS rather than a new one. This closes the AI-assistant gap between SAS 9.4 Foundation and SAS Viya without requiring a platform migration, and respects the need for regulated organisations to choose or self-host their own LLM provider rather than use one fixed backend. ... View more

Add list control (or other method of selecting multiple items) in to report and page level control to give users the ability to select multiple items when filtering. I appreciate that the report and page level filter sections are designed to be small and compact this could be achieved using a popup list box or similar to the image.      ... View more

We would appreciate it if the following features could be developed for Visual Investigator: Support multi-selection from a value list. Support multi-selection from hierarchical value lists. For example, consider a hierarchical value list with the following structure: Level 1: A, B, C Under B: B1, B2, B3 Users should be be able to select multiple values from the same value list, including multiple child values within the same branch of the hierarchy, such as B1 and B2, in a single field. These enhancements would provide greater flexibility when working with value lists and hierarchical reference data, while eliminating the need for workarounds ... View more

It would improve usability if users could configure the display format for datetime values. Currently, when a datetime format is selected, the value is always displayed with seconds and milliseconds. The client would like the option to display only the hours and minutes, without seconds or milliseconds.   We are using Visual Investigator 2025/09, Release: 20251209.1765255106922. ... View more

It would improve usability if users could print documents directly from the system without first having to download them. This would streamline the printing process and reduce the number of steps required.   We are using Visual Investigator 2025/09, Release: 20251209.1765255106922. ... View more

SAS Studio users can upload files to SAS Server (assuming the showServerFiles is enabled) but it seems like there is no UI option to change/modify the files' permissions.  This is especially useful when uploading SSH keys for Git integration. I upload the keys using SAS Studio but then I want to  change the private key's permissions to 700 but cannot find a way to do it within SAS Studio's UI. I am sure there are more use cases in which this will be useful.     ... View more

It would improve usability if numeric identifiers (such as IDs) were displayed without thousands separators (for example, commas), preserving their original format.   We are using Visual Investigator 2025/09, Release: 20251209.1765255106922. ... View more

Hello, It would improve usability if users could drag and drop attachments into the object. ... View more

The SAS Information Catalog distinguishes between Basic and Advanced Features. However, as a SAS administrator, I have no way to control or restrict access to these individual features. Even SAS Consulting was initially unable to explain how compliance with the licensing model can be reliably enforced and had to investigate the matter further. For an enterprise platform, this is not acceptable. There should be a clearly defined license enforcement mechanism that ensures users can only access the features covered by their license and allows administrators to centrally manage and enforce license compliance. And that’s not just the case for the Information Catalog. ... View more

Under the terms of the licence, it should be possible for the Data Profiling Agent in SAS Information Catalog to analyse SAS Compute libraries even in the Data Governance Basic version.  In large SAS environments, there are hundreds of SAS libraries, and every authorised SAS Viya user should be able to make use of this great feature.  From a business perspective, it does not make sense to purchase a Governance Advanced licence for this purpose. ... View more

I would prefer it if only those users who have access to the data could view the profiling results in the SAS Information Catalogue. I work for the largest health insurance provider in Germany, and we have strict regulations regarding social and health data. In this context, it is unacceptable for the profiling results to be visible to every authorised SAS Viya user, as, for example, individual variable values are displayed.   For this reason, we are unable to make use of this very useful  and cool feature.  From my perspective, this is a capability that one would typically expect from a data governance tool. 😉 ... View more

Where relationships are displayed, consider providing a centralized view of all relationships without requiring users to switch between object types. Alternatively, hide object types that have no relationships to the current object. This would simplify navigation and make it easier for users to find relevant relationships.   We are using Visual Investigator 2025/09, Release: 20251209.1765255106922. ... View more