About CaseySmith

CaseySmith · ‎06-13-2016

As @jklaverstijn mentioned, the XMLV2 engine is a sequential-only engine. EG's data grid did not previously support viewing XMLV2 (or XLSX engine data, since also sequential-only). However, we added support for both of these in EG 7.12 HF2 (Y39002), which you can install via Check for Updates (in EG 7.11 or later, and if your admin allows) or from here: http://ftp.sas.com/techsup/download/hotfix/HF2/Y39.html Casey

CaseySmith · ‎05-30-2016

If your SASAppVA workspace server is defined in the same metadata server as your SASApp workspace server (you see both in EG's Servers view), then it would be trivial... add another program node and have the second program run on SASAppVA (select it from the "Selected Server" dropdown on the contextual toolbar of your second program). The first program could run on SASApp and the second on SASAppVA. Draw an explicit link between the two programs to ensure they run in the order you wish. (You can create a link by right-clicking a node and selecting "Link Program to..." or by clicking the right side of a node and dragging to another node.) If your SASApp and SASAppVA workspace servers are in different metadata contexts, then it requires other approaches (ex. SAS/CONNECT, writing data to permanent location accessible by both environments, etc.).

CaseySmith · ‎05-27-2016

No, unfortunately EG 7.12 does not currently suggest data set variables in PROC SQL (neither the SELECT statement, nor WHERE statement, etc). (I agree, it would be nice if it did. Hopefully in the future.) EG 7.12 does suggest data set variables in other contexts (ex. DROP=, KEEP=, VAR, BY, etc.) and the data set variable suggestion pop-up window can be re-opened via Ctrl+Shift+V in supported contexts. Casey

CaseySmith · ‎05-20-2016

It appears pressing F3 or F8 in a log window currently runs the entire process flow the program is in. That is not intuitive. If focus is in the log, I would not expect F3 or F8 to run anything, since a log is not "runnable" (for the same reason there is no Run button on the contextual toolbar for logs, but there is for programs). I'll enter this as a suggested improvement in our tracking system, such that F3 and F8 do not run anything when focus is in a log.

CaseySmith · ‎05-20-2016

Just saw this thread with the same question: https://communities.sas.com/t5/SAS-Enterprise-Guide/SAS-EG-keyboard-shortcuts-previously-open-drop-down-list/m-p/269433#M18659 See Chris' reply in that thread about using the free AutoHotKey tool to possibly fill in the gap.

CaseySmith · ‎05-20-2016

Unfortunately, as Haikuo guessed, EG does not currently have a keyboard shortcut for accessing the "Recently Viewed Items" dropdown. That would be a nice improvement.

CaseySmith · ‎05-20-2016

Hi @juanvg1972, Yes, EG OnDemand for Academics is supported with .NET Framework 4.6. However, the installer might unnecessarily require .NET Framework 4.5.1 to be on the machine at install time (won't proceed if it doesn't find it). If that is the case, and you only have .NET 4.6 on the machine, (and willing to go through the trouble), you should be able to safely temporarily install .NET Framework 4.5.1, install EG OnDemand for Academics, then uninstall .NET Framework 4.5.1 and EG OnDemand for Academics would automatically use .NET Framework 4.6 instead. Casey

CaseySmith · ‎05-20-2016

The first (editable) text pane is where you type the advanced expression, which requires you to use column names (can't use column labels) to reference variables. That secondary read-only text pane is the "show column labels" version of the advanced expression. The only difference is that it shows column labels (if present), rather than column names. As such, it is the more human-readable version, depending on the column names and labels (if used). The secondary pane only appears if the "Use labels for column names" option in EG's Tools->Options->Data->Data General tab is checked. So, you can hide it by unchecking that option. (It would have been nicer to have a way to hide that secondary pane right in the dialog.)

CaseySmith · ‎05-20-2016

Since the error message indicated, "failed to provide the SAS workspace" and it worked when the user tried later, it may have been a network issue that was preventing EG from being able to make a connection to the SAS workspace server.

CaseySmith · ‎05-20-2016

Prior to EG 7.11, the log summary view did not find errors in the log if there wasn't a space immediately after "ERROR:". So, to workaround, make sure you put a space between "ERROR:" and your error message. This was fixed in EG 7.11, which recognizes errors with or without a space after "ERROR:". Casey ps- Fortunately, almost all SAS-generated errors start with "ERROR: " (with a space), so really only an issue for user-written errors.

CaseySmith · ‎05-20-2016

Hi @pchegoor, The bug you mentioned (also noted here: http://tsdsrv05.unx.sas.com:7777/iw/docs/sasnotes/fusion/57/979.html) was fixed in 7.12 HF2, which released today. You should get notification in EG 7.12 the next time you start EG or if you click Help->Check for updates (if your admin allows Check for Updates) that the new update (7.12 HF2) is available. You can then single-click to install it. Or you can download and apply the traditional way from here: http://ftp.sas.com/techsup/download/hotfix/HF2/Y39.html Sorry for the inconvenience that bug may have caused. We too were disappointed that it slipped through. Casey

CaseySmith · ‎05-20-2016

If you have EG 7.1 or later, try out the "Upload to LASR" task, which both moves the data to LASR and registers it for use in SAS Visual Analytics. Right-click the data set in the EG project tree or process flow that you wish to upload and select "Upload to LASR", then follow the simple wizard.

CaseySmith · ‎05-20-2016

I'm fairly certain you are encountering this: http://tsdsrv05.unx.sas.com:7777/iw/docs/sasnotes/fusion/57/979.html It was fixed in 7.12 HF2, released today. You should get notification in EG 7.12 the next time you start EG or if you click Help->Check for updates. Or you can download and apply the traditional way from here: http://ftp.sas.com/techsup/download/hotfix/HF2/Y39.html

CaseySmith · ‎05-12-2016

Hi CatCol, (Sorry, just noticed I never responded to this. Following up now.) Perhaps you have an older EG or server version... EG started sending the APPNAME property in version 6.1. So, you will need EG 6.1 or later (running against a 9.3 or later server) to see APPNAME= in the object spawner logs. Casey

CaseySmith · ‎04-07-2016

Remember, the paths specified in code are from the context of the server. So, when you specify "C:\HH_Providers.pdf" in your code, SAS is trying to write that file on the SAS server's host machine. The user that you are logged into EG as is evidently not authorized to access "c:\" on the server.

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