If there is a list of values (copied from excel or dataset or text file) that need to be used in where condition, strings need to be in quotes separated by comma. How about giving power to Find & Replace in SAS EG (Ctrl+H) like Notepad++ does.   For example I have: Acura Audi BMW Buick Cadillac Chevrolet Chrysler Dodge Ford I want them : "Acura","Audi","BMW","Buick","Cadillac","Chevrolet","Chrysler","Dodge","Ford" Step 1: Open notepade++ and paste the values. Step 2: Remove leading and trailing blanks: Go to edit->Blank Operations->Trim leading and trailing space. Step 3: Put quotes: Open Search>Replace… in Notepad++ (Ctrl+H) Select Regular Expression and in find what add (.+) and in replace what add “\1” and click replace. This will add quotes to the words listed in the file when replaced.     Step 4 Separate by comma: Now in Find what add \r\n and in Replace with add just comma (,) as shown in screenshot.         ... View more

All the major SAS string handling functions have a macro equivalent: %index %substr %scan %upcase %length   Especially when using %scan, one often has to use %sysfunc(countw()) to initialize a macro loop.   So I propose to create a macro equivalent of countw, namely %countw, similar in function to %scan with regards to delimiters and modifiers. ... View more

The TERMSTR option is used to define the record delimiter (End of record marker) on flat files. This options does not accept hex values, which is very odd as record delimiters normally aren't standard characters. The syntax   TERMSTR='0c'x   should be supported. The example above was chosen because '0c'x is often used by Hadoop files.   As an aside, this whole option could do with a cleanup as in the following example,   data t; file "%sysfunc(pathname(work))/t.txt" termstr='0c'x; put 'A' / 'B' / 'C' ; run; data _null_; infile "%sysfunc(pathname(work))/t.txt" termstr='0c'; input; putlog _infile_; run; 1- The x is suffix ignored in the first data step's file statement and the delimiter is set to string '0c'.   So the file is 9 bytes long and contains:    A0cB0cC0c   2- In the second data step, SAS somehow finds these 2 nonsensical records:     A0cB   C0cB       ... View more

If I assume that my RDBMS supports ISO8601 for date, time, and datetime literals (and if it doesn't, it should), then it would be convenient if SAS did the same.     Sample Code:   %let date=%sysfunc(date(),e8601da.); %let time=%sysfunc(time(),e8601tm.); %let datetime=%sysfunc(datetime(),e8601dt.); %put &=date; %put &=time; %put &=datetime; My results as of the time of this post:   27 %put &=date; DATE=2016-08-16 28 %put &=time; TIME=10:32:06 29 %put &=datetime; DATETIME=2016-08-16T10:32:06 I only have SQL Server to test against right now, but these values all "work" for SQL Server:   SELECT CAST('2016-08-16' AS DATE) ,CAST('10:32:06' AS TIME) ,CAST('2016-08-16T10:32:06' AS DATETIME) But not for SAS:   data _null_; date="&date"d; time="&time"t; datetime="&datetime"dt; put date=date9. time=time. datetime=datetime. ; run; If SAS supported the ISO8601 standard, this would make the interchange of date, time, and datetime literals easier when querying data between SAS, RDBMS (implicit pass-through) and RDBMS (explicit pass-through). ... View more

Add an option to PROC FORMAT that would allow us to type a description when we define the format. Currently, we can type such a description after the format is defined, using PROC CATALOG. Specifically, I would like to add the DESCRIPTION option to the PROC FORMAT statement. This option should work the same way as it works in the MODIFY statement of the PROC CATALOG procedure (I just want to do it sooner -- when I define the format, not in a separate step later) One good use for such a description is to include the identity (&sysuserid) of the person who makes or changes the format (as soon as he/she changes the format, not in a separate step) Ideally, PROC CATALOG would show a USER field in the output, and this field would populate automatically with the value in &sysuserid as soon as that person defines the format, but this might be too difficult, so I'm just asking to add the description option to proc catalog. Related discussion: Format Description at the Time of Definition ... View more

Request It is requested to enable dynamic text features in VA. It should be feasible to include in reports specific values (measures & dimension) as single objects and or combined (text&images&values). It should be feasible to include in va reports values and text and images and have the possibility to define formatting also with conditional formatting (e.g including icons and images as per specific rule) Use case/Workarounds It has been required to include single values in Reports with a specific formatting in order to give right evidence to kpi’s and key values (#number of contracts, budget, …) The workaround identified so far is to use cell of a standard VA table, but the formatting opportunities are limited and result is not effective. Using of the table workaround is complex for user and requires to design in fix format (Standard VA feature should enable to ensure adaptive) Considerations Feature could be very useful for improvement usability and effectiveness of reports Feature is expected to be available both for web and for Mobile and as standard Va feature so that report in WEB and in Mobile can be the same (avoid duplicating development of report). As per our evidences feature is already available in many BI tools competitors. ... View more

When performing linear regression from EG, our data scientists always want to save the parameter estimates to a data set for use in subsequent tasks. in the current versions of EG they have to manually insert code to add outest= option. after running the task with inserted code, the outest data set does not appear on project canvas, the user has to select it manually from server list and add it to the project canvas and connect it to the regression task.   idea: add an option to the linear regression task to save parameter estimates to a data set (generate code: outest=<data-set-name>) and add that data set to the project canvas. ... View more

We have a crosstab based report with 30+ columns. The column headers take up a lot of space. In order to save space it would be very convenient to be able rotate the column headers 90 degrees, like in Microsoft Excel for instance. ... View more

Internally, we would like to show year over year growth of 20% with 25% being a stretch goal. Standard visuals only support one target for a targeted bar chart. Also we are unable to show the data values for this target within the report, only within the data tip values.   Here is my current solution build using the custom graph application:     We would like to see the high/low target range shading similar to below:   This was built with the customer builder as well, but it does not look the best in the standard data styling skin consistent with the rest of our reporting.   -shawn ... View more

Can the following be implemented? : A colon preceding a suffix selects with variables with the common suffix, as would select variables AC and BC in the second data step below, without error: data have; AC=1; AD=2; BC=3; BD=4; AEC=5; BED=6; data _Null_; set have; format A: z4.; putlog _All_; data _Null_; set have; format :C z4.; putlog _All_; run; Colons sandwiching a search term as a use of colon wildcards, as in:  format :E:  z5.;     Also see sasnrd.com = Drop or Keep Variables With Same Suffix ... View more

Please add a toggle switch that would alternate between displaying formatted and unformatted values in SAS data viewers.  Similar to the existing option to view Variable Names versus Variable Labels.  The current display always hows value labels and one has to resort to time-consuming tricks to unmask the relationship between value and format.  A simple toggle would permit a quick access to information hidden by the formatted values. ... View more

When using pre-assigned libraries and right-clicking to display Properties, Enterprise Guide shows the storage path in metadata (/Shared Data/Libraries/.....). I would prefer to see the physical path of the library instead (as is shown for libraries assigned with the BASE engine). At least this should be a configurable option, or (ideally) both locations should be displayed. ... View more

Often times I use the WHERE button in the dataview which works great. It would be very helpful to be able to quickly sort the dataview either in the normal view or while using the WHERE button. This would make validating data much faster than having to create a new query. ... View more

When a certain expression is used to create a new variable: create table ouput2 as select put(Team,$Ffmt.) as Team_Category, count(*) as No_Customers and the same expression is used in the group by: group by put(Team,$Ffmt.) the SQL compiler should recognize this and act as if the new variable had been used instead: group by calculated Team_Category and avoid the (accidental) remerging with the original data ... View more

Hello,   A lot a usable space is lost on the SAS Logon Manager web page. I find it useful to reuse part of it  in order to display Important/Urgent messages to the incoming users :   for example, maintenance scheduled with outage at < day, time> , system operation scheduled at etc.   I know it's not officially permitted but I have already modified the Logon HTML code , inside the deployed hierarchy of SAS Web App Server to allow this. It worked fine altough the content update process was risky and required editing manually a file on the midtier machine ...   Wouldn't it be nice to allow this kind of feature to SAS 9.4 admins, using an update channel well-devised and somewhat easy to use (for instance, a Stored Process with text fields and some little typographical enrichments to be selected optionally like Red colored text, bold font etc.) ? This would replicate the Message Of The Day (motd) broadcasting feature known for a long time on Unix systems or SAS-wise the (little-known) NEWS system option.   To illustrate my point, I've taken the liberty to take a caption of such a Logon modified page (courtesy of SAS Institute ; )    See picture above.   Thanks for considering this idea !   Ronan   PS I've tagged this idea with SAS Studio even though it's broader actually ... View more

At the moment, it is possible to create a single connection to a single LDAP server and in that connection, 2 queries, a single query for users and a single query for the groups.   In the past, the User Bulk loading could allow an array of queries, for both the users and the groups, and also a certain pagination based on number of observations or based on alphanumeric order and you could split the queries.   It would be really nice and useful in SAS Viya, especially in SAS Visual Analytics environments, where it is expected a usage of thousands of users per organisation , the possibilities to:   Create multiple queries, for users and for groups, having different baseDNs and to split internally those queries in additional queries, based on number of observations and/or starting letter (alphanumerical)   ... View more

We all know that SAS develops its software in separate teams, but it can be really annoying when it becomes apparent that several associated teams haven't planned together how a SAS procedure will work.   I'm going to take as an example PROC IMPORT, which is part of Base SAS, but is also included in SAS/ACCESS. When you run the following program all the variables created begin with VAR, i.e. VAR1, VAR2, VAR3, VAR4, VAR5, etc., and this would also be true for DBMS=TAB and DLM: PROC IMPORT FILE = "test.csv" DBMS = CSV REPLACE; GETNAMES = NO; RUN; However, using similar PROC IMPORT code for DBMS=EXCEL, in SAS/ACCESS for PC Files, will create variables beginning with F, i.e. F1, F2, F3, F4, F5, etc.: PROC IMPORT FILE = "test.xls" DBMS = EXCEL REPLACE; GETNAMES = NO; RUN; More shocking though is using PROC IMPORT code for DBMS=XLS or XLSX in UNIX or Windows, in SAS/ACCESS for PC Files, as this will create variables with no prefix at all, i.e. A, B, C, D, E, etc.: PROC IMPORT FILE = "test.xls" DBMS = XLS REPLACE; GETNAMES = NO; RUN; This inconsistency even extends to using GETNAMES = YES too when there are multiple columns with the same label.   If you want to import a CSV file, instead of an Excel file, or indeed import an Excel file in UNIX, then the subsequent processing step will have to be updated to use the new variable names (annoying!). Why can't the procedure be consistent, or, at least, have a parameter, like PREFIX=, that allows users to choose the prefix? ... View more

  Some functions truncate strings in PROC SQL: data TEST; length X $300; X=repeat('X',299); run; proc sql; create table WANT as %* Var Len; select trim(X) as TRIM %* 300; , translate(X,'a','b') as TRANSLATE %* 300; , scan(X,1) as SCAN %* 300; , left(X) as LEFT %* 300; , prxchange('s/a/b/',1,X) as PRXCHANGE %* 200; , cat(X) as CAT %* 200; , case when 1 then cat(X) end as CASE %* 200; from TEST; quit; But this can be fixed in some cases by forcing the variabel length:   proc sql; create table WANT as %* Str Len; select trim(X) as TRIM length=300 %* 300; , translate(X,'a','b') as TRANSLATE length=300 %* 300; , scan(X,1) as SCAN length=300 %* 300; , left(X) as LEFT length=300 %* 300; , prxchange('s/a/b/',1,X) as PRXCHANGE length=300 %* 300; , cat(X) as CAT length=300 %* 300; , quote(X) as QUOTE length=302 %* 302; , case when 1 then quote(X) end as CASE length=302 %* 0 <==; from TEST; quit; The case statement however does not pass on the defined length to the executed function. It should.   ... View more

Currently VA doesn't allow users to use existing aggregated measures when creating new ones (i.e. it cannot perform an aggregation on an aggregation). The only solution is to perform these calculations prior to uploading the data to LASR, which can be prohibitively resource intensive when dealing with a large number of possible variable combinations.   This feature would give designers much more control when creating new measures within VA and provide workarounds for many complex data requests. ... View more