Dear SAS R&D,     I have already described case, it is in the link below: https://communities.sas.com/t5/SAS-Customer-Intelligence/Changing-version-status-of-read-only-campaign/m-p/400520   There are 2 campaign states: read-only and do-anything. I'm sure adding more campaign states will work wonders. Possible states: - an approved (read-only) campaign that can be run without the possibility of modification - an approved (read-only) campaign, which status can be changed from approved to design   This option can be added in the business context settings. Similar to the option to change approved campaigns to Read-Only status.   But the best solution in my opinion is the creation of a fully-fledged campaign state tuner. On the similarity of how the process of creating and editing roles in the SAS MC is now implemented in the User Manager tab.                                                 ... View more

At the moment it's not possible in SAS Visual Analytics to calculate the t-distribution based confidence interval for the mean of a given sample using t-quantiles (depending on samplesize/degrees of freedom and confidence level).  It's only possible to calculate the confidence level based on assumption of normal distribution (using fix z-quantile values) of the mean which is not appropriate if the standard deviation of the population is unknown and has to be estimated by the std.dev. of the sample. Obviously there is a function in SAS called TINV(df, alpha) but it's not available in SAS Visual Analytics. We hope that you will include this basic function in inferential statistics in SAS Visual Analytics.   Thank you in advance and kind regards   Nicolas Matzinger Dipl. Natw. ETH Statistik/EDV   Post CH AG Geschäftsbereich E-Health Baumackerstrasse 46, 4. OG  CH-8050 Zürich ... View more

For the SURVEY procedures in SAS (e.g. PROC SURVEYMEANS, PROC SURVEYFREQ,...), the documentation says "If an observation has a weight that is nonpositive or missing, then the procedure omits that observation from the analysis".   However, this can give incorrect standard errors when enough PSUs and Stratums from the sampling design are removed due to persons with zero weight. In fact, the DOMAIN statement exists for this precise purpose, in order to keep all observations in the analysis rather than subsetting with a WHERE statement and removing valuable information for standard error estimation. However, persons with zero weight are removed from the dataset before DOMAIN is implemented. Thus, using DOMAIN in this case is moot.    Currently, the only solution I've come across is to either change the weight from zero to a very small positive number (e.g. 1E-60), or to set it to a positive number (e.g. 1) and flag this group with an indicator variable, which is then used in the DOMAIN statement.   It would be nice to have a simple option in the SURVEY procedures which wouldn't require editing the original dataset in order to get the correct standard errors. ... View more

SUGGESTION:  Add the START= option for model selection in PROC GLMSELECT. This option is already available in PROC REG, PROC HPGENSELECT, and PROC PHREG.   The only way to automate backward stepwise model selection in SAS in to use SELECTION=BACKWARD and set START equal to the number of independent variables in the MODEL statement. PROC HPGENSELECT produces different variance estimates than PROC GLM and PROC REG, and PROC REG does not allow CLASS variables, so adding this feature to PROC GLM will fill a hole for a basic statistical procedure in SAS. ... View more

Left joins can increase the number of rows in the left table if there are multiple matches in the right table.   I know we can use the data step to select only the first or last match a join finds, but this parameter should be something the user can select inside of EG's Query Builder/Join Tables function, instead of having to dip down into code.    I can't seem to find a way to replicate this in the drag and drop of EG.  Have to use code directly.  If I use EG Query Builder and a left join on NameID, Bob shows up twice in the Final table as his NameID matches two orders.  The code below only selects the first order found because of the first.nameid statement; strike it and Bob shows up twice.   Ideally, you'd be able to handle multiple matches on the join inside of the EG Join Tables layout directly.      ... View more

Trying to use SAS supplied FXdb227 driver delivered with SAS Data Quality (DataFlux) doesn't work with db2 version 11.1 ... View more

   Hi,   There would be nice if you can display a message/show confirmation dialog after clicking on "Run process flow" in SAS Enterprise Guide, something like "Are you sure you want to run process flow?". It sometimes happens accidentally to click on "Run process flow" and then I have to stop all the tasks. I am using SAS EG version 7.13 HF5 (7.100.3.5486) (64-bit).   Thank you! Cristian Stancu ... View more

In SAS VA when you add a rank to display the top 3 brands of cars - you get it. When you then add a second rank to get the top 3 of a second element, it does not yield the correct results, but rather treats this as though it was its own rank, rather than a sub rank of the 'cars' rank.   Please add a multiple level rank ability, so that in tables we can show the top n of the top x.   Thanks,   Happy to add more detail / screenshots to clarify message if needed. ... View more

See https://communities.sas.com/t5/SAS-Enterprise-Guide/Remap-Enterprise-Guide-hotkeys/m-p/341360 ... View more

Add the SELECTION= option to PROC LIFEREG to enable variable/model selection capabilities.   ... View more

When accessing help internet explorer is launched to access help online.   SAS Support say "I can confirm that the behaviour you are seeing is expected and by design. Please note that the help of some of the procedures point to a specific User's Guide, such as the SAS/STAT User's Guide in the case of the GLIMMIX procedure, and these User's Guides are not part of the offline help files that are installed on your computer. Thus, it is not possible to prevent these from being redirected to the SAS Documentation website."   There are many circumstances when working offline is essential or simply the only option due to lack of internet coverage. The change to online help from locally installed help is a regressive step which limits the functionality of SAS. ... View more

Below code submitted in EG 6.1 but I suspect it's applicable in DMS, Studio, etc.   Below are test scenarios based on a comment in my actual code (the 2nd comment is just to generate 262 characters)     * Workaround SAS's inability to include the datalines statement inside a macro ; /* This is a really long comment to generate 262 characters after the single quotation mark. I sure wish the macro compiler could treat a single quote within a comment as just that, a comment, instead of treating the single quote as a special character. It works with slash-asterisk style commenting but not other commenting styles. */ data foo;x=1;run;     Submit this...so far, so good.     %* Workaround SAS's inability to include the datalines statement inside a macro ; /* This is a really long comment to generate 262 characters after the single quotation mark. I sure wish the macro compiler could treat a single quote within a comment as just that, a comment, instead of treating the single quote as a special character. It works with slash-asterisk style commenting but not other commenting styles. */ data foo;x=1;run;     Submit this...oops.   But at least submitting ;*';*";*/;quit;run; fixes the issue.     But now I want to comment out the entire code block.  So I use the "trick" of wrapping the code in an uncalled comment block:     %macro comment; * Workaround SAS's inability to include the datalines statement inside a macro ; /* This is a really long comment to generate 262 characters after the single quotation mark. I sure wish the macro compiler could treat a single quote within a comment as just that, a comment, instead of treating the single quote as a special character. It works with slash-asterisk style commenting but not other commenting styles. */ data foo;x=1;run; %mend comment;     Submit this...oops again.   At this point, submitting ;*';*";*/;quit;run; doesn't work, nor does %mend;;*';*";*/;quit;run;     At this point all I know to do is restart the workspace server.   However, submit this:   %macro comment; /* Workaround SAS's inability to include the datalines statement inside a macro */ /* This is a really long comment to generate 262 characters after the single quotation mark. I sure wish the macro compiler could treat a single quote within a comment as just that, a comment, instead of treating the single quote as a special character. It works with slash-asterisk style commenting but not other commenting styles. */ data foo;x=1;run; %mend comment; That works.   So, whatever the macro and/or SAS compiler is doing in this last example, do this for the previous examples as well.   If a statement is a comment, then the contents of the comment shouldn't "break SAS".   I suspect that this could be harder than it appears, and would require a lot of testing for backwards compatibility.     But this issue bites me occasionally, when I forget and use a single quote in a comment, and in this case I lost a couple hours worth of WORK datasets when I had to restart the workspace server.     ... View more

It's famous problem with the locks on SAS datasets. I think that it will be great to "make the SAS Software great again" and final deal with that issue. Often the options in EG (Tools>Options>Data >) doesn't help and the only solution is to kill the process by Administrator.    My proposal is to consider the solution that allows releasing the locks by the user who is dataset creator from the Enterprise GUI level. ... View more

The idea is to implement for SAS users the Tree ring that shows in the best way the outcome of the decision tree.  This element was a part of a very early version of EM and was very helpful and easy to understand by business people. We have a tree map but it's not easy to understand by most of them. Maybe it's worth of consideration because it will be simple to implement in next release. ... View more

Many times we've had to sort a table by some variables, then use another proc sort to eliminate duplicate observations based on a subset of the previous variables of the sorting. Eg: proc sort;   by var1 var2 var3; run; proc sort nodupkey;   by var1 var2; run;   It would be really useful if we could merge those two processes in one, to reduce the reading/writing load. Especially when dealing with larger tables, every rewrite in disk takes a LOT of time. The example above could be reduced to: proc sort nodupkey=var2;   by var1 var2 var3; run;   Regards, C. ... View more

In the dashboard there are some thumbnail graphs showing the status of the SAS environment. On the x-axis the time is displayed as (-8hr, -6hr, -4hr, -2hr, now). If, for some reason, the graphs does not get updated, there is no way of detecting this without drilling in to the details. It would be better if there was a way to change the labels to actual time or to change the word "now" to the current time. ... View more

Provide a system option for specifying default behavior of Proc Format. Sorted/Notsorted.     ... View more

Add option(s) "Group datasets and views in separate folders" (and)or "Group notes in separate folders" to dialog "Tools"►"Options" under "Project Views"►"Project Tree" ... View more

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