In VA 6.3 Explorer it is possible to export the shown chart to PNG.   In the Designer and Viewer, there should be a similar function.   As for now, there is no easy way the end users of my reports can grap and use what they see on the screen.   On the basis of https://communities.sas.com/thread/53198 ... View more

We have been generating reports in VA (6.3) and for some of those reports we simply would like to embed them in an iframe so our other applications can display them in various contexts. Would be even better if sections of the reports could be pulled separately. Is there a way SAS can implement this?   Note: Previous version 6.2 seems to be able to do that. Rendering in VA must have changed. From users perspective this seems like a feature taken away with 6.3. ... View more

It seems as though the JSON (JavaScript Object Notation) format is quickly becoming a standard alongside XML with respect to data acquired via web services.  I'd like to see PROC JSON incorporate the ability to read JSON-format datasets in addition to the already-existing write functionality. ... View more

In a simple stacked bar chart, such as on a graph like such: proc sgplot data=sashelp.prdsale; vbar year/response=actual group=quarter groupdisplay=stack; run; It is often desired to have the response value labeled on each stacked bar.  This can be done with annotation, but it is cumbersome and causes difficulty when using SGPANEL (for example) to combine multiple charts.  Currently, datalabels create tables on top or bottom when used with stacked bar charts, but do not overlay the groups.  Instead doing this: proc sgplot data=sashelp.prdsale; vbar year/response=actual group=quarter groupdisplay=stack datalabel datalabelpos=center; run; or something like that would be simple, and as the data tip already contains this information, this should not be complex to implement. ... View more

I just came from an EXCELLENT talk on Enterprise Guide for Programmers at Boston Area SAS Users Group, by Chris Bost.   The talk is available at: http://www.basug.org/downloads/2013q2/Bost.pdf   Not surprsingly in a room full of programmers, during the discussion the question came up, "can I do a batch submit?"   And I think currently, the correct answer is "no, you can't, because EG is an interactive environment, in the same (similar) way that DM SAS is an interactive environment."   Chris B. helpfully pointed out that you can schedule an EG project, which accomplishes something like a batch session.   But here's the thing.  When I programming in SAS, I was taught that I should ALWAYS submit my final code as a batch job.  There are two main benefits.  1. You ensure that your code works on it's own, and isn't working (or failing) because you have a lot of temporary datasets / formats / macro variables / whatever assembled junk sitting in your work library.  2.  You get a log file.   During discussion it was suggested by someone that might be nice if EG just had a "batch submit button."  I think it's a grand idea.  If I press "Batch Submit", I want EG to spawn a new SAS session on the server, and execute my program in that new session, then return the results as usual. Getting a log file would also be nice, but that is a separable issue (and PROC PRINTTO is available as a workaround).   Now when using EG, it seems like there are approximations of ways to ensure that you have a clean session to run your code in: 1.  Schedule the flow. 2.  Write a macro that will try to clean up your session (delete temp datasets/filerefs/librefs/macro vars/etc etc) 3.  Disconnect from the server and then reconnect.  (I feel like EG is unhappy with me when I do this, maybe it's because my code is linked instead of embedded in the project, I think EG loses track of the links when I disconnect) 4.  Close EG and restart it.   To me, those are all work arounds for not having a batch submit  button.  Sounded like a grand idea to me, so wanted to throw it out to the group.   --Q.   (edited 12/10/13 to add link to slides from presentation, and make clear that "Chris" is Chris Bost, not Chris H.) ... View more

PROC OPTMODEL: add a COV= option to output the covariance matrix ... View more

PROC OPTMODEL: allow syntax to declare recursive implicit variables with the IMPVAR declaration ... View more