Background: We've implemented, among others, two entities, accounts and transaction. Those are related to each other with a relationship, which is represented by a bridge table, and a respective traversal. On the account details page we've placed a related objects control, leveraging that traversal to display the transaction being related to an account. There are a few accounts with more than 2000 transactions related to it. Visual Investigator cannot display those transactions in the related objects grid: Changing the "Node expansion size limit (hard limit)", which is 2000 per default, to 5000 doesn't help, because there will not be more than 2000 transactions fetched and displayed, probably due to some hardcoded restriction. We investigated the API-Calls in the background and as the main player we identified the path-search-api (POST svi-sand/paths?limit=2000&expansionLimit=2000 with a filter in the Payload) According to the documentation (pathsSearch | SAS Developer Portal) a start and limit parameter is available suggesting that paging might be possible, but it is not used by the Related Objects control.   Our Change request: Our suggestion is to offer an option to activate paging for the Related Objects control to support displaying accounts with more than 2000 transactions related to it. Sorting, Filtering & Exporting might only adjustable in the control setup & not avalable to endusers;  ... 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

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

When using custom steps in flows, the name can be customized, but not the image. If a flow consists primarily of custom steps, images would be more helpful for clarity:   ... 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 would like to raise a feature request for future consideration for SAS Visual Investigator    You can implement highlighting (color code) on Object Manager results and Advanced Search results. Basically, users should be able to see color code on Objects (like a Case., Alert) in the object manager results and Advanced search results if the admin can configure like to show the field Orange when the Status is Under Investigation or show a red color in the field when Disposition is Certified Fraud.   Thanks,  Raja  ... View more

When dates are viewed in the VI GUI they are automatically displayed in the user's local time zone BUT when you export to Excel they are in UTC? This is confusing our users as quite rightly they expect to see the same data in both formats, this should be a bug fix and not a feature request IMHO... ... View more

Currently at https://communities.sas.com/t5/SAS-Product-Suggestions/idb-p/product-suggestions I am able to view "Hot Ideas", "New Ideas" and "Top Ideas" but I cannot see "My Ideas"    It would make life easier if one could easily locate his ideas to review their status ... View more

Currently when you write parquet files via the sas libname engine the parquet types are fully determined by the informat only.  That is to say if you have a numeric variable with a datetime20. format and no informat it will be written to the parquet file as a double.     The feature request is that if no informats are specified SAS should use sensible default types based on the format.  It is very intuitive that a datetime20. format column should be written as a timestamp thus users should not have to be burdened for defining informat types for what should be obvious conversions.  ... View more

Currently when SAS reads and writes parquet data files via the libname parquet engine labels are dropped and thus cannot be restored when the file is read back in.  Parquet though supports arbitrary metadata storage in the file header.     The suggestion here would be for SAS to store column labels in the parquet metadata and then retrieve and restore them when reading the file back in.    For reference the R arrow::write_parquet() function already does this by storing R specific attributes in the "R" field of the parquet files metadata.  ... View more

There should be an option to cancel SAS Viya jobs in the UI of the Environment Manager.  ... 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

Tanzu is a popular K8S platform provider - please add official support for it like you support OpenShift and cloud providers. ... 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

SAS Visual Investigator - Page Builder Interface - GRID - Column Editor We suggest : - Adding the option to declare numerical data type columns in GRID - Making numeric filters accessible in GRID columns   When Grid is populated from a REST URL Response, numeric datatype fields end up being displayed as character data. Columns in Grid , therefore, lack filters that are specyfic for numeric datatypes (Is greater then, Is less than or equal etc.). In addition, since fields are not displayed as numeric, "Locale for regional formats and sorting" format changs do not apply to them.   Grid column configuration already allows declaring DateTime columns. We propose the option to configure numeric datatype as well.   ... View more

  In SAS's official documentation, the Disaster Recovery solution is addressed using the backup-restore method. However, for some of our clients, real-time workloads are very intensive, and the time lost during backup restore does not meet SLA requirements. With the advancement of new technologies, we believe that the Disaster Recovery solution should now be approached through replication, rather than backup-restore. In our opinion, structures like SAS's integrated Postgres should also be automatically replicated within the Disaster Recovery solution. ... View more

Currently, it is not possible to stop discovery agents in the Information Catalog. In a corporate environment with a lot of data, it may be the case that the agent is running for hours and you want to stop the agent to change the configuration. This would be very helpful, not to mention essential, for the real-world use of the Information Catalog. ... 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

Hi SAS Community!   The idea for this ballot is to include SAS Packages Framework macros (https://github.com/yabwon/SAS_PACKAGES/blob/main/SPF/SPFinit.md) into Base SAS and Viya.   Mature open source communities (e.g. R, Python, or TeX groups) allow users to share code (even complex one) in an easy "transportable" form of packages. I believe that the SAS Community is also one that could use such form of "code exchange". The SAS Packages Framework is a set of macros which allow you to build SAS Packages. (The framework is open source and MIT licensed)    To build or use a package macros from the framework need to be available in the SAS session. So now it requires additional effort for both developers and users who want to work with SAS Packages - the framework has to be downloaded and included for a SAS session. Why no add the framework macros to the SAS deployment so both developers and users could focus on making and using SAS Packages rather than on setting up "environment" to do so?   Articles describing the idea are here and here Video introduction to the idea can be found here and here.   All the best Bart ... View more