The display of data label inside the stack bar is a basic requirement.
Please put this as the top priority.
A node with a dataset-like icon with the name of a macro variable. When created, this node is listed with other avaiable datasets and dataviews in the process flow or project. When this "dataset" is assigned to a task the dataset defined in the macro variable is used in the sas code generated byt he task. If implemented as purely a macro variable with a dataset's name, then the linked-to dataset's indexes will available to the procedure statement.
One example of code that can't exist using EG and the Query Builder task:
%let dataset=SAShelp.CARS; proc sql; select model from &dataset; quit;
In a way of speaking, its like a view of a dataset implemented in EG.
I feel that a number of users would like to have this feature in PROC LIFETEST which handles right-censored data.
PROC LIFETEST estimates the quartile confidence limits via Brookmeyer & Crowley(1982, Biometrics) but does not do any testing or multiple comparisons for such entities.
Brookmeyer & Crowley(1982, JASA) presented a test for medians that could serve as a model here.
Brookmeyer, R. and Crowley, J. (1982), "A Confidence Interval for the Median Survival Time," Biometrics, 38, 29-41
Brookmeyer, R. and Crowley, J. (1982), "A K-sample Median Test for Censored Data" Journal of the American Statistical Association, 77, 433-440
Add similar options to SAS/Access interface to Sybase IQ as done for SAS/Access interface to Oracle.
At the moment charactersize is always tripled for each char column but tables usually have only a few columns with special characters.
Because of the increased total number of bytes performance suffers a lot when switching SAS to unicode.
(These options are described in the SAS 9.2 unicode server documentation.)
provide the ability to control the behavior of data items and folders when opening an information map
I would like to be able to create a table that alternates the row color to distinguish between cities. However, the variable cities is not unique as it is possible for the city to appear in the table more than once. I would like to keep and have each different city the same color and alternating colors between different cities......any suggestions would be greatly appreciated...thanks.
SGPLOT Currently an ODS Graphics procedure such as SGPLOT can create an editable graph....but the destination is limited to the file types of .SGE and .PNG (according to tech support). It would enhance the product further if an ActiveX driver could generate these graphs to ODS destinations such as RTF and HTML. This combination exists for the "older" SAS/Graph procedures (e.g. GPLOT) and we'd like to see it available for the newest procedures as wel.. Thanks you.
Many times when Call execute() is used the parameter is a call to a macro and the step containing the call is used to insert parameters for the macro. This usually involves some sort of messy concatenation or substitution. In my proposal,
In effect Call Mexecute (parm1, parm2, ...parmn) would be equivalent to Call Execute (cats('%',parm1,'(', catx(",", parm2, ..., parmn), ');') ) [untested] or the like.
PX-Web is an API and interface for delivering statistic data. It is used by at least several statistical bureaus in Scandinavian and Europe. It has an powerful API which make it possibly to automatic download data. In R, there are an simple interface to PX-Web.
My suggestion is that SAS develop an interface to PX-Web API. Even better, an interface as an tool in Enterpris Guide and SAS Studio. I think it will benefit the users in Europe much.
I think it will be an easy work for a skilled programmer to do it. With my limitied skill, I have mangage build SAS code for the download, but still I have to redo the code for every task.
PROC GCHART: add the ability to control the color of the axis plane in a 3d bar chart
Add Deming regression to an existing regression procedure (such as PROC REG or Proc GLM). Include an option for weighted Deming regression.
It would be very useful if you could control (through Roles/Capabilities) who can submit libname statements and possibly to where (limitable to certain servers/locations/types etc.).
This will enable central management of data through Management Console and prevent proliferation of data.
add the ability with SAS/Secure to encrypt the MPI communication to be FIPS-104.2 compliant.
The NVALID function is supposed to validate a SAS name. The first parameter is the potential name. The second parameter, validvarname, can be one V7, ANY, and NLITERAL or it can be left blank. If blank, the parameter will use the setting of the VALIDVARNAME system option to decide whether the string is a valid name under the current settings.
The problem is that the function does not demand the name-literal-surrounds ('...'n or "..."n) even though any actual usage of the value WILL require this to surround the name. It does not validate the string as a name but rather its potential to be used as a name if first fed to the NLITERAL function. So NVALID will return true on both the following forms:
%put %sysfunc(NVALID(This Name Should Not Be Valid, NLITERAL)) ;
%put %sysfunc(NVALID('This Name Should Be Valid'n, NLITERAL)) ;
when it ought to return false on the first call since a macro variable with that string cannot be used as a SAS name. This limits its usefulness since the primary purpose of this function is to validate a potential name. It gives false positives. ANY fares no better...in fact, it is arguably worse because it doesn't properly evaluate the length if the name-literal surround is present.
Since macros may have been developed which rely on this behavior, the simplest method would be to add two additional options that behave as one would expect of a validation function. Perhaps NAMELIT (to require the name-literal surround and validate assuming ANY) and SYSNAMELIT (to require the name-literal surround and validate based on the system option).
at this time i can only show descriptive data about a restaurant, item, customer, etc. in a table across a very wide row.
i know that VA is not a report builder but the ability to show details about a customer would be very helpful
these details are data items such as, name,address, city, state,zip,phone,fax,email,etc.
this data object could be designed to only show data from one record.
it would be in an info window and allow many data items to be show in a small amount of space.
Add this to the top section of the script testing doc please. That way the doc can be shared w/o having to cut/paste info from the email...of course after finding that email in inbox ;-}
<snippet from email sent to start the round1 testing>
You will be accessing two GUI
interfaces for the SAS Cloud AppManager portals:
will not be able to log in to the subscriber portal until you are defined as
either an administrator or an end user
that users can be associated with only one SUBSCRIBER/tenancy.
Perform the “SUBSCRIBER administrator” and the “SUBSCRIBER end user” tests from