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

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. ... View more

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 ! ... View more

EG should update the program icon (highlighted below) at the same time the process flow program icon is updated. Using example in screen shot, blue circle should changed to a red X at the same time the process flow program icon changes. The Log Summary is also not updated while a program is running. Both features are incredibly helpful due to the notification of errors/warnings prior to completion, and were present in EG 7. ... View more

HPSplit is in Base SAS/STAT as a standard offering. Random forests are a staple of predictive modeling. Move HP Forest out of SAS Enterprise Miner and put it in the SAS/STAT product. Random forests are 20 years old now, it is nowhere near a novel technique.   There are other packages that need moving over but this one is a no-brainer, at least to me. ... View more

Frequently a SAS programmer needs to both sort and divide a dataset. Typically these tasks are satisfied via a two stage program:   (1) divide the dataset, (2) sort the parts. Something like:   data _asia (where=(origin='Asia')) cars_europe (where=(origin='Europe')) cars_usa (where=(origin='USA')) /view=_asia; set sashelp.cars; run; proc sort data=_asia out=cars_asia; by msrp; run; proc sort data=cars_europe; by msrp; run; proc sort data=cars_usa; by msrp; run; Enabling proc sort to do both of these tasks (with syntax such as below) would often significantly reduce input/output activity, and offer a bit of code simplification:  proc sort data=sashelp.cars out=cars_asia (where=(origin='Asia')) cars_europe (where=(origin='Europe')) cars_usa (where=(origin='USA')) ; by msrp; run;   Of course, the multiple output datasets need not be mutually exclusive like the example above. ... View more