About CaseySmith

CaseySmith · ‎07-16-2019

EG 7.15 HF8 surfaced this problem... EG 7.15 (prior to HF8) was incorrectly storing editor settings in this 8.1 registry location (as you noted): HKEY_CURRENT_USER\Software\SAS Institute Inc.\Enhanced Editor\BIC_8.1 (should have been BIC_7.1) 7.15 HF8 updated EG 7.15 to use this corrected location instead: HKEY_CURRENT_USER\Software\SAS Institute Inc.\Enhanced Editor\BIC_7.1 However, that means any editor customizations that you made prior to that are still in the BIC_8.1 registry location instead of the BIC_7.1 registry location (where 7.15 HF8 is now looking). The easiest way to get your customizations back is to "copy" the registry settings from BIC_8.1 to BIC_7.1 via the export/import instructions Tech Support provided to @EStrom1. Casey

CaseySmith · ‎07-15-2019

Yes, the (SDW-based) installer is a little misleading (gives the impression that it will replace 7.1, since an "upgrade"), but rest assured, as @SASKiwi noted, it will install 8.1 and leave 7.1 intact, thus installed side-by-side. Casey

CaseySmith · ‎07-15-2019

@Kurt_Bremser, yes, it would make a lot more sense. Unfortunately, there isn't currently another mechanism (that I'm aware of) for delivering non-free software through SAS Release Engineering. We are working with other teams to make this easier in the future. Casey

CaseySmith · ‎07-15-2019

Here is the location of the EG standalone installer within your SAS depot: <SASDEPOTROOT>\standalone_installs\SAS_Enterprise_Guide_Independent_Installer\8_1 (SASEnterpriseGuide81_x86_x64.exe) As noted, subsequent EG 8.x releases (ex. 8.2, 8.3, etc) will be able to be upgraded to via EG's Check for Updates feature. I posted additional details here on why we chose not to allow Check for Updates to take you from 7.x to 8.x: https://communities.sas.com/t5/SAS-Enterprise-Guide/SAS-EG-8-1-how-to-obtain/m-p/567517#M34029 Thanks for the feedback. We agree and hope to make it easier to get EG in the future. (Without having to download a massive depot.) Casey

CaseySmith · ‎07-15-2019

I would also make sure you have the latest hotfix applied for your EG version. Casey

CaseySmith · ‎07-15-2019

Hi Kevin, A Search feature has been built into EG, but it is not as robust as Chris' plugin. You should still be able to use Chris' tool if desired. We do plan to enhance the search capabilities in a future release. Casey

CaseySmith · ‎07-15-2019

Yes, we removed the Filter and Sort task "quick launch" button from the data toolbar. This was an intentional change and part of a larger effort to simplify the UI. Sorry, no, you cannot customize the toolbar. You can either use the Query Builder for your filtering and sorting (which is still available with one click from the toolbar), or as you noted, add the Filter and Sort task as a favorite, thus only two clicks away, or double-click the Filter and Sort task from the Tasks pane with your desired input data active. Casey

CaseySmith · ‎07-15-2019

As you all noted, conditional logic added to a process flow does not currently get exported as SAS code. Manually coding conditional logic (as suggested) is the closest solution. Casey

CaseySmith · ‎07-15-2019

Yes, we are working toward having support for SAS Studio My Tasks in the next releases of EG and AMO (8.2). It is a high priority. Casey

CaseySmith · ‎07-15-2019

A user-defined style that you edit/create in EG's Style Manager is just a css stylesheet. Here is how you can use an existing css stylesheet in ODS statements: https://support.sas.com/rnd/base/ods/templateFAQ/Template_csstyle.html#existing So, find the physical location of your .css file (URL field in EG's Style Manager), then copy the .css file to a location on your webserver that your html pages can reference. And more doc on css stylesheets with ODS: https://support.sas.com/rnd/base/ods/templateFAQ/Template_csstyle.html Casey

CaseySmith · ‎06-19-2019

You will need to download a new depot to get EG 8.1 (which was released yesterday (6/18)!). Then you can use the standalone EG installer or the traditional SAS Deployment Wizard to install it. EG 7.1x versions will not notify you or support updating to 8.1 via Check for Updates, since 8.1 is a major new release. Details: This was an intentional decision because the project format has been versioned (as we now typically do at major release boundaries). Thus, once a project has been saved in EG 8.x, it is no longer backwards compatible with 7.1x versions of EG. For this reason, if you share EG projects, we recommend coordinating upgrading with your colleagues, so you use the same EG version. Note: Since EG 8.1 is a major version and not an update, EG 8.1 can coexist (be installed side-by-side) with earlier EG versions. Note2: Future 8.x releases will be able to be installed via Check for Updates from earlier 8.x versions, since they will be updates (minor releases) in the 8.x family. Casey

CaseySmith · ‎06-19-2019

Hi @ramya4, The PowerShell code you shared is attempting to connect directly to a SAS Workspace Server and then submit SAS code to it (similar to as described in the blog post https://blogs.sas.com/content/sasdummy/2013/03/13/using-powershell-with-sas-workspace/). The problem with your PowerShell code below is that "getting the content" of the .egp file ($program = Get-Content "C:\TestCode.egp";) is not going to return SAS code. An EG project (.egp) file is a compressed proprietary store (ex. a zip archive). If you get the contents of a text-based file (ex .sas file) instead, then the PowerShell code looks like it should work (it should submit the code in your .sas file to a remote SAS Workspace Server). However, if your goal is to run the actual EG project (the .egp file) rather than just submitting some SAS code, then you really want to use the EG automation interface rather than connecting directly to a SAS Workspace Server and submitting code. The EG automation interface will handle these things for you. These blogs describe how it works and have some PowerShell examples: https://blogs.sas.com/content/sasdummy/2012/04/17/doing-more-with-sas-enterprise-guide-automation/ https://communities.sas.com/t5/SAS-Communities-Library/Doing-More-with-SAS-Enterprise-Guide-Automation/ta-p/417832 Or, you can click File->Schedule in EG to created an EGScript.vbs file to see an example of using the EG automation interface (running an EG project). Then you could port that from VBScript to (or do something similar in) PowerShell. Casey

CaseySmith · ‎06-17-2019

There appears to be a problem with a SAS Studio 3.7 update (C7W002) that was recently applied to SAS OnDemand for Academics. We believe it also impacts SAS Studio 3.71 hotfix (C2L006 and C2L005). We are working on a fix. There are a couple ways to workaround the issue in the meantime... 1. Switch to the Visual Programmer perspective, by clicking SAS Programmer on the SAS Studio toolbar and changing to Visual Programmer. 2. If you are running SAS Studio in a non-English locale (ex. German (de), Spanish (es), French (fr)), run it in the en locale instead (put "?locale=en" on the end of the url, or replace existing "locale=<locale>" in the url with "locale=en"). Sorry for the inconvenience. We will provide a fix asap. Casey ps- There is also now a notice on the Status Page: https://status.oda.sas.com/?context=us-west-2a

CaseySmith · ‎06-13-2019

Ok, thanks. You could try unchecking the "SAS Report" results format (ODS results) and see if it makes a difference. It would also be helpful to know the answer to my previous question... How long does it take EG to run "Partial V4.sas" (run the exported code in a new EG session, rather than running the original EG project)? Were the earlier times you posted (~88 mins) for EG how long it took EG to run the original EG project or for EG to run the single program file "Partial V4.sas"? Assuming it was the amount of time it took EG to run the original EG project, I'd like to know how long it takes EG to run the single program file (Partial V4.sas), so we can then compare that to running the same program in Base SAS. Casey

CaseySmith · ‎06-11-2019

It sounds like you exported all the code from your EG project to "Partial V4.sas" and then compared the time it takes the original EG project to run to the time it takes Base SAS to run the exported code "Partial V4.sas". How long does it take EG to run "Partial V4.sas" (run the exported code in a new EG session, rather than running the original EG project)? It should be very similar to the amount of time it takes Base SAS to run it, especially if EG isn't configured to generate ODS results (if you don't have any results formats checked in EG's Tools->Options->Results->Results General). Casey

Online Status	Offline
Date Last Visited	3 weeks ago