About CaseySmith

CaseySmith · ‎02-20-2017

What version of EG do you have (in Help->About)? This sounds similar to an issue that was addressed in an update. Make sure you have the latest update/hotfix.

CaseySmith · ‎02-20-2017

Prior to EG 7.12, the Ctrl+S keyboard shortcut saved the EG project (which you can see on File menu), but did not automatically save changes in externally referenced files. EG would then prompt you (as in your screenshot) to save any unsaved changes in any open external programs. We agree, this was not intuitive behavior. You expect Ctrl+S to immediately save what you are working on, no questions asked. Starting in EG 7.12, we improved this behavior. Ctrl+S is now a more intuitive, contextual save. So, if you are working with an external program and press Ctrl+S, it saves the program file, without prompting (as you would expect). If you are working with an embedded program, Ctrl+S saves the project (since embedded programs are saved within the EG project). In addiion, we added a Save All operation, which saves the project and any open files. So, to get rid of the prompt, I suggest upgrading EG to the latest version (7.13).

CaseySmith · ‎02-14-2017

Click and drag the little region at the top of the vertical scrollbar (top-right corner of screenshot below, which green arrow points to) or the little region to the left of the horizontal scrollbar (already dragged/split in screenshot below): Once you start dragging from that region, it turns into a splitter, which splits the two views. If you drag both the vertical and horizontal, you'll have four views.

CaseySmith · ‎02-14-2017

@jasu wrote: I definitely agree that EG is far less productive than DM when it comes to window navigation. As a long-time DM user who had to migrate to EG recently, I'm finding EG's inability to have multiple data sets open in separate, undocked windows to be a serious drain on productivity. I continue to keep my fingers crossed that an EG update will be released in the very near future to address this severe limitation. Hi @jasu, this is an area we wish to improve EG as well and are in fact working on designs to address this in a future release. We want to provide a lot more flexibility in managing the windows and content in your EG workspace, including docking, floating, leveraging multiple monitors, comparing content/reports/data, etc. I obviously can't promise when (a large effort), or even if, but it is high on our list.

CaseySmith · ‎02-14-2017

Just wanted to point out that starting in EG 7.13, the Copy Files task (previously a custom task, written by Chris Hemedinger) is built into EG. It can be accessed from the Tasks->Data->Copy Files menu.

CaseySmith · ‎02-13-2017

I'll also mention, there was an issue viewing XLSX engine data in the EG data grid (would cause EG to hang) that was resolved in EG 7.13. If the problem you are seeing is specific to XLSX engine data (ex. doesn't occur with BASE engine data), you may be encountering this issue. If you are encountering this issue, upgrading to EG 7.13 should resolve. Casey

CaseySmith · ‎02-10-2017

Hi @SINNETIC, Yes, the HTML document builder (Tools->Create HTML Document) was removed in EG 6.1. It was deprecated primarily because it became increasingly difficult to maintain reliably as a result of changes to the ODS-generated HTML. A point-and-click alternative does exist, though it is not as direct. Rather than joining HTML output directly, it involves generating SAS Report output, joining the SAS Report output in the SAS Report builder (File->New->Report), then exporting the report as HTML. Casey

CaseySmith · ‎02-03-2017

You are welcome! Yes, that is correct... for existing projects (created in versions prior to 7.13), the option will be Continue execution, so the previous behavior is preserved by default. We didn't want to change the behavior of an existing project unbeknownst to the user. As you noted, new projects will default to Stop current branch.

CaseySmith · ‎02-03-2017

@RyanK wrote: This is another situation where it would be helpful to have a process flow stop in its tracks on a failure. That is currently also tedious to implement. We added a feature in EG 7.13, which does exactly this. You can now control the action EG takes when an error occurs during execution. You can set the option ("Action to take on errors during execution") for the whole project via File->Project Properties->Code Submission. Or you can override it individually on each node, by right-clicking the node, selecting Properties, Code Submission. The default option value is Stop current branch. The pre-7.13 behavior was to continue execution. Here is a screenshot of the option and the three choices. Note: The Query Builder node with the error (ex. a Query Builder) will still break its link, since the process flow attempts to reflect the results of the most recent run. However, at least all subsequent nodes are halted, limiting downstream break-up. Note 2: Turning off Auto Arrange on the process flow (by right-clicking inside the process flow and toggling Auto Arrange) will help preserve the process flow layout when links are unintentionally broken.

CaseySmith · ‎02-01-2017

Please attach the log that was generated from your code submission. Perhaps something about the specific log is throwing off the Log Summary view.

CaseySmith · ‎01-25-2017

If you save the log with a .log extension, then add the .log file to an EG project, the Log Summary view will be displayed and will summarize the log. When you select an error, warning, or note in the Log Summary view, the corresponding line in the log will be selected, same as for logs generated within the project. However, there are a couple differences from a log generated within the project... 1) The ERRORs, WARNINGs, and NOTEs in the log aren't currently colored (red, blue, and green). 2) The "Go to Program Source" and "Go to Log Source" menu items are disabled. (I expect the "Go to Program Source" menu item to be disabled, since no linked program in this case, but was expecting "Go to Log Source" to still be enabled. If the log was saved with a .txt extension, EG opens it as a plain text file (doesn't realize it is a log), thus Log Summary view not shown. It would be nice if EG offered an "open as log" option, so user could explicitly tell EG to open it as a log.

CaseySmith · ‎01-25-2017

@SASKiwi is correct... if you want to use multiple workspace servers from the *same* program, SAS/CONNECT is the way to go. However, you can also leverage multiple workspace servers using an EG connection profile by associating different workspace servers to different program nodes. This does mean you have to breakup your program into separate program nodes (maintain as a process flow rather than a single program file), depending on which parts you want to run on different servers.

CaseySmith · ‎01-23-2017

I think the biggest benefit of connecting directly to remote servers (rather than rsubmit) is the direct access to data and results. For example, in EG's Servers view and file open dialog, you'll have direct access to the libraries, data, and files on the remote server. Whereas, if you are using rsubmit, you'll only see your Local server and the libraries, data, and files on it. Also, when you run code directly against a remote server, the results are seamlessly sent back to EG. I believe with rsubmit more work is needed to get the results back. You can certainly use rsubmit, but there is added convenience connecting directly to remote servers.

CaseySmith · ‎01-23-2017

">If you have a functioning SAS server that you can access with SASStudio and rsubmits, does that imply you have a SAS MetaData Server?" No, it does not. Perhaps you do not have a SAS Metadata Server running and that the connection information you provided in the EG profile was to your remote SAS Workspace Server, rather than a metadata server? Admins typically use SAS Management Console (SMC) to login to and manage the metadata in a SAS Metadata Server. If you can't login to it from SMC, it's probably not a metadata server. If you have a Local SAS server, you can rsubmit to it from EG to submit (indirectly) to your remote server. Otherwise, to submit directly to your remote server from EG, you will need to define an EG profile with the host and port to a running SAS Metadata Server, which should contain a server definition to your remote SAS Workspace Server.

CaseySmith · ‎01-23-2017

The intent (and what I observe) is as Tom mentioned... "If there's nothing connecting the programs, EG will try to execute them in a left-to-right, top-to-bottom order." (*in the process flow*) Re-ordering nodes in the process flow should change the order of execution, since EG executes items left-to-right, top-to-bottom order. Changing the order in the project tree (rather than process flow) has no effect on execution order.

Online Status	Offline
Date Last Visited	‎10-09-2025 07:58 AM