SAS Product Suggestions

ferrickc · ‎10-20-2023

Denodo is a data virtualization tool capable of building intricate and efficient data structures connecting disparate data sources. Data virtualization is critical in enterprise environments due to the wide variety of data sources a large organization would possess. Our organization has recently implemented Denodo, but we are experiencing significant compatibility issues with our SAS 9.4 infrastructure as we are reliant on the generic SAS/ACCESS Interface to JDBC. In troubleshooting sessions with Tech Support, we have resolved one issue only to encounter another, over and over again. It has become clear that the source of these incompatibilities stem from the generic JDBC connector. An ACCESS engine specifically designed to communicate with Denodo would provide a true solution to our technical issues and frustrations. We hope that this connector would be compatible with SAS products including SAS 9.4, SAS Viya 3.5, and newer products.

GeorgeBonanza · ‎12-05-2023

It seems proc import can retrieve data from Excel if the data is in a sheet by itself using the "sheet=" statement, known range i.e., "A1:C10", or named range using the "range=" statement. What I don't see is an easy way to import the data if it is an Excel Table. Something like a "table=" statement in the code below to accomplish this would be extremely helpful. I apologize if this already exists, I couldn't find anything. Thanks in advance for your attention to this matter. proc import out= WANT datafile= "C:\ExcelFile.xlsm" dbms= EXCEL replace; TABLE= "TBL"; run;

RichardHorgen · ‎12-04-2023

As far as I understand, there is currently no option to use explicit pass-through with cloud data exchange. This is a major drawback for customers migrating to Viya, that over the years have made extensive use of this functionality on the SAS 9.4 environment. One of the main reasons explicit pass-through has been used, is to make use of non-standard SQL functions available from the database vendor. One such function that will require a lot of rewriting of code is the Qualify-statement available at several vendors. Thanks in advance for your attention to this matter.

rodenpt · ‎07-07-2023

We have a use case where our company files are stored in Sharepoint. It is currently difficult to access these files on VIYA and they manually have to be uploaded. We would like to be able to connect SharePoint to VIYA such that: 1. SharePoint files and folders are visible in SAS Studio Explorer folder tree and can be manipulated like standard files residing on the SAS Server. 2. SharePoint files are directly accessible to SAS Studio flows. 2.1.Allow a file residing in SharePoint to be imported/exported using the standard SAS Studio Import/Export functions.

foobarbaz · ‎04-05-2022

SAS Studio currently supports text, xml and python files in conjunction to the SAS program format. Markdown is a widely used text markup format used in repositories of source code to document the functionality of a project and have the markup rendered in a variety of file formats such as HTML, LATEX, PDF etc. Markdown files are used widely in git hosted repositories and is a defacto standard within the community. Currently, if a user tries to open a markdown file, the user will be prompted to download the file instead of opening within the application. This stops users from being able to effectively view git repository help docs or create developer and api documentation for SAS projects without leaving SAS Studio and using some other third party application. Ideally SAS Studio would allow the following: Viewing of Markdown files with syntax highlighting of markdown elements View rendered markdown as html in a separate tab similar to results rendering currently used for ODS Allow creation and editing of files in markdown format with syntax highlighting.

sdut · ‎03-21-2022

Hi, We are facing a strong showstopper with the current limitation of not allowing to mix INNER and OUTER joins in queries. Which is impacting the usage of our data providing system, to which SAS connects to. Giving more options in the "libname jdbc" statement would give the user the ability to "match" the query generation in SAS with the real capacity of the underlying system using JDBC. Here are a few of those options that would be nice to add: - underlying system supports using inner and outer joins together - this limitation in particular is much more impactful than the others. Most DBMS systems allow that today so SAS should allow that for JDBC datasources. - underlying system does not support JDBC escape sequences - pass custom connection properties (Mapping for java class Properties) - sometimes some JDBC drivers do not support passing all parameters as URL. Thank you !

LeslieBarwick1 · ‎08-23-2023

I've noticed that when i import a DI job that uses either a SQL execute or a user written code transform. The user written code that is imported to VIYA is on a single line and you must scroll to the right to see the code. It would be useful to either auto format the code upon import or provide a auto-format button. At the moment my work around is to copy the single line of code and then create a new .sas program, paste the code in and then auto-format. I then have to paste my code back into the node within the swinlane and then save. On the screen shot below, my original code has 100s of lines of code however it is imported onto a single line. The .spk is a DI job. We are on a 9.4 m6 AIX 7.1 deployment... not sure if this is anything to do with the operating system.

raavi2002

Hi, I think it would be beneficial to have Generation Data group like dataset in SAS similar to the format used in Mainframe. Generation Data Groups (GDGs) are group of datasets related to each other by a common name. The common name is referred as GDG base and each dataset associated with the base is called a GDG version. You can set the limit of the related files(generations). We can easily keep track of all generation of data sets. Any particular generation can be referred easily. We use lot of datasets which regenerates daily , monthly , yearly etc.. Consider I need to create daily transaction data for the month of May. If Generation Data Group is available, I would define the base like "Tran_May2024". Then I would just create dataset daily in the below way. Data Tran_May2024(+1); -- This will create the next available version. set work_tran_table; run; If need to point current or earlier version i would use the dataset below. Tran_May2024(0) - Latest Version Tran_May2024(-1) - Previous Version Tran_May2024(-2) - 2 versions back If I need the whole month data , i just refer the base Data work_tran_may; set Tran_May2024; --This would all the version available in the base run; you can have options like below LIMIT – To limit the maximum number of generations. NOEMPTY – Uncatalog only the oldest generation in GDG when the limit is reached. EMPTY – Uncatalog all the generations when a limit is reached. SCRATCH -Physically delete the dataset(generation) which is uncataloged. NOSCRATCH – Don’t Physically delete the dataset(generation) which is uncataloged. This would help a lot when we create lot of datasets which are created in a repeatable fashion. Thank Ravi

vmurray

It would be nice to be able to copy text from an individual cell in the list table. This is possible in a crosstab but it would be nice to mimic the excel function of copying from a regular table/cell for the list table.

Michael_Steer · ‎04-04-2024

Date formatting in SAS VI / LEI is controlled by browser language settings. For example if your browser language setting is English UK then dates will be UK formatted in the UI. Whereas, if your browser language setting is English US then dates will be US formatted in the UI. Clients don't always have access to change language settings on company laptops and therefore feel it would be beneficial for SAS VI / LEI to have a global language setting in VIYA / Environment Manager that automatically formats all dates to the preferred style of the client.

EyalGonen · ‎03-20-2024

Please consider adding a feature to allow CAS server elasticity in the form of auto-scaling for SAS Viya 4

MattJans · ‎03-19-2024

Stata has a very handy documentation/transparency/reproducibility metadata function that allows users to add custom, verbose notes to a data file (as metadata). See more information here: https://www.stata.com/manuals/dnotes.pdf. As far as I can tell, SAS doesn't do this (can label a data file, but limited space to do so). The maximum length of one note is 67,784 for a single note and multiple notes can be added to a data file (e.g., when doing something to/with it and saving). The notes are numbered sequentially, so can be used as a change log, e.g., 1. Saved raw data file after downloading from the web. 2. Created recodes for vars X-Z. 3. Copy of data file used in publication. See other examples in the link above. Obviously, this information can be listed in a custom log or in code, but what's better than attaching metadata about a data file to the file itself? Thanks for considering!

Michael_Steer · ‎02-25-2024

In SAS LEI we are using the Tripwire functionality. One of the OOTB fields for this entity is called Generate Email which is a Boolean field. On the LEI page template that we have designed for our client the end user is required to check the box to either true or false to request the required email. This field is displayed on the page template as a check box with the pre determined value of false. The client is requesting that this check box is automatically checked to true from the outset rather than the end user having to check the box. From conversations with Tech Support and R&D we know that this is not possible within the current solution and have suggested a feature request whereby the person building the SAS LEI configuration can set the Boolean value / check box to either true or false when designing the page template.

gm7 · ‎01-25-2024

With all these changes around SAS needs to be innovated in order to stay competitive with this market and make SAS Viya more competitive tool with the other firms by producing Excel report with Jobs Flows and scheduling jobs that has dependance. It would be a great idea and invention, if you ask your engineer to add this functionality PROC DOWNLOAD Statement into SAS VIYA, that will allow Developer to send excel files directly into windows share drive, in addition to sending file into Unix. 😊

CAKSTX · ‎01-04-2024

I'm fairly consistent with how I set up my SQL joins and for some reason the auto-complete on the from line below, will expand to AS BETWEEN. I'm ending the line on AS B but the enter key always completes BETWEEN. I'm wondering if it would be possible to make an exception to the auto-complete in this common scenario and not have B autocomplete to BETWEEN. This is more of an annoyance but I could imagine how many folks are having the same issue. PROC SQL; CREATE TABLE CM_STATS_JOIN AS SELECT A.*, B.CN AS TOTAL_CM FROM SW_STATS AS A LEFT JOIN CM_COMBINED AS B ON A.'PUBLIC HEALTH REGION'N=B.REGION; QUIT;

dlbarron · ‎12-20-2023

Recently, to resolve issues that I have encountered with Viya 3.5, I have had to add multiple entries into the logging.level definition, to generate debugging information in various logs. After the issues were resolved I had to set the logging level for each new configuration item to OFF. I was surprised to discover that there was no way to delete the items. This seems like a needed feature, the ability to delete configuration items in general, if not from the logging.level specifically. Thank you.

Rob_D · ‎10-19-2023

Hi, we are running SAS 9.4 (TS1M7) on z/OS 2.5. We use the FILENAME statement to allocate a concatenation of datasets under the same fileref. The SAS limit for the number of concatenated datasets under the same fileref is 200. (see https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/hosto390/n0yrspsfthx1w5n1gyt6rgzh3qsu.htm ) Would it be possible for SAS to extend that to a larger limit in a future release please? I think the limit has been 200 for a long time now and 200 datasets is not that many nowadays. Thanks.

FloydNevseta · ‎03-31-2023

For process flows with Auto arrange turned on, the default arrangement is vertical. There should be an option to allow a horizontal arrangement of process steps. For process steps that create many data sets, the vertical alignment causes excessive scrolling. If steps are arranged horizontally then one can view many process steps on a single screen without scrolling regardless of the number of generated data sets. Please see the post below where I describe a workaround for this issue with screenshots. Navigating SAS EG process flow map that is too large to scroll through - SAS Support Communities It seems that allowing a horizontal auto arrange option will alleviate this problem.

lc_isp · ‎01-30-2023

Time ago, when I was working with RapidMiner, I took profit a lot by having sub-processes grouping the single graphic process' elements into kind of "black box" (programmers may call that "subroutines"). Now I'm working with SAS Enterprise Guide 7.15, under SAS 9.4, and I feel the lack of such custom elements. It's nothing which changes that much the way SAS EG is working already: mostly a "visual help" to unclutter the current project's steps. Moreover, those (custom made) subprocesses could be re-used, along the project's steps, if given the ability to be parametrized (by means of configurable fields and/or in/out variables, like prompts), like every SAS element. As far as I know, is nowadays possible to do the same by using a SAS program which groups features carried out by graphical elements (like query builder, sort data, etc.) into a single program "icon" (element). What I can see, is many SAS persons hardly work with programs, as they know much more the data than the algorythms (I'm more a programmer than a data scientist, that's why I think more to algorythms than data). With complex projects, it happens to have many elements to manage and, sometimes, we may want them to be "just grouped" so to see their results, more than the single item's activity. Let me show why I was thinking to subprocesses. Me and colleagues are developing a project which is already complex enough, having many elements per step. At some point, we felt the need to add "test points" to the process, to know, from outside the system, "at which point the whole project was executed, and with which timing" and to let other colleagues, which uses that project but not having SAS access, the same informations: the project is scheduled to start everyday at 01:00am so, when they start working, having such "test points" added, they know if all gone well, and me and developers to know the performances/timing, by looking at exported small PDF files' date/time. (I'm pretty sure there are better ways to carry out the same functions but they're just an excuse, here, to allow me to show you why I was thinking to subprocesses). In blue you can see the "test points" we added, not that good view: they're made by 4 elements which I expanded above in yellow. It was probably better to have a single, custom made, "Test Point" element, including the above ones and to be configured with the table's name to read, and the PDF path/filename to export. That's my need of the moment, but I'm sure the very same can be told for many projects having recurring "sparse elements" cluttering the project's steps. As far as I've seen, up to now, SAS EG components' hierarchy is made by: project (the whole "container") ! steps ! elements (even grouped into programs) The idea is to insert subprocesses in the hierarchy: project ! steps ! subprocess (custom made elements grouping elements) ! elements

SASware Ballot becomes SAS Product Suggestions

Build an ACCESS engine to Denodo

Import Excel Table using proc import

Introduce explicit pass-through option in Cloud Data Exchange

How do I connect SharePoint file system to VIYA file system

SAS Studio Support for Markdown Files

JDBC SAS/ACCESS: More options for query pushdown generation

When importing a .spk into viya, auto format code so it doesnt appear on a single line.

Generation Data Group in SAS

Copy text from List table column/cell

Global language setting in SAS VI / LEI

Allow CAS Server auto-scaling

Allow adding a note as metadata on a SAS data file

Set Check Boxes / Boolean Values in SAS LEI to true

Proc Download to Windows Share Drive in SAS VIYA

Maybe a bug? PROC SQL Auto Complete Concern

Suggestion for removing "New Configuration" entries for Viya 3.5

Filename concatenation limit of 200 on z/OS

Provide a Horizontal Arrangement Option to the Enterprise Guide Process Flow Auto Arrange Feature

SAS Enterprise Guide: add subprocess to "group elements" and to be reusable elements too

SAS option to run from cursor

Introduce explicit pass-through option in Cloud Data Exchange

Provide a Horizontal Arrangement Option to the Enterprise Guide Proces...

EG: Possibility to include external programs in several process flows.

SAS Enterprise Guide: add subprocess to "group elements" and to be reu...

Internal File Diff for EG

EG: Customizing Dialog Fonts

Move code and other items from one EG process flow to another