Thanks Robert! That's a nice looking dashboard. You're right though....That is an ugly way to have to get there. I dropped a note to tech support as per your suggestion, to get/keep this on the radar. I'm hoping that there's an undocumented technique/option that has recently become available to save me from tweaking all that code. I really appreciate you getting me started though. Thanks again! Keith ... View more

Maybe the only solution is to have the user replay the doc store (in its entirety) for the last batch run and then use the document builder etc to pull out meaningful pieces. I'm assuming that would run pretty fast, even with 100 or so output objects. Or, maybe we could have a stored process with a limited number of selection criteria that would run proc document in the background and pull a smaller set of the user's info back. BTW...Would that report builder be able to pull-in both report and gplot/gchart output? We're just now getting ready to go to 4.2 and it looks like in 4.1 the graph would have to be saved as an image first prior to bringing it into the New/Report interface (based on my limited testing). Thanks! Keith ... View more

Thanks Richard. I'll take a look at the New Report functionality. The thing that I'm really struggling with is trying to integrate results from batch processes with EG. That is, trying to find a flexible way to surface those batch results to users of EG so that they can replay them or build a report based on pieces of the output (without having to re-run the job within EG). However, it seems there's no way to read that document item store from within EG except via proc document. Even this might be suitable, if I could have the batch job label the pieces of output with meaningful labels that were visible via proc document. However, I'd ideally like to be able to import the document item store into EG. Or, maybe surface this document store via the SAS add-in for MS Office? Thanks again for all the input! Let me know if you have any more thoughts. Keith ... View more

Thanks Cynthia! I really appreciate it! ... View more

I believe I ran into this problem previously and used the following tableeditor tagset option to force the proper data type. data_type="String,Numberx,Numberx,Numberx,Numberx,Numberx,Numberx,Numberx" I don't have time to test but as I recall, this solved a similar problem that I had. Keith ... View more

Thanks Cynthia. I'd like to take advantage of the document store for some large batch processes but I'm concerned about how we'll manage the contents. Ideally, I'd like to push project output to a document store so that users could selectively put together and replay portions as needed (for sales presentations, meetings etc). I've done this before in non-EG SAS and it was very nice. However, we are in an EG only environment and we have quite a bit of output being generated. This wouldn't necessarily be a problem but trying to determine which GLM or print etc has the info that the user is looking for, without the interactive window, seems messy. This is complicated by the fact that the batch process may run different processes/procedures depending on the input parms. Do you have any suggestions regarding how this can best be managed? From what I've seen there's no way to "label" the procedures at run-time (Although even if there were, I don't think we could see the labels without the interactive window). From a dev standpoint, I would like to use this functionality to provide some added flexibility in our production reporting. However, the idea of having to manage the potential ripple effect of document references when a new proc is added (without the advantage of the interactive window for identifying/verifying output objects etc) is keeping me from moving in that direction. I really would like to take advantage of this functionality so any suggestions you have are appreciated! BTW...could the document window could be called via a .NET application and integrated into EG that way? Thanks Keith ... View more