Angela offers tips on using the SAS Business Intelligence solutions. She manages a team of SAS Fraud Framework implementers within the SAS Solutions On-Demand organization. Angela also has co-written two books, 'Building BI using SAS, Content Development Examples' & 'The 50 Keys to Learning SAS Stored Processes'.
If you create (in SAS Management Console) a user group with parentheses in it's name you cannot assign a Portal page to that group. A NullPointerException results instead. The workaround is "don't do that", or remove the parentheses if you did. While I haven't exhaustively tested the boundaries of this
If your SMC or other metadata-based SAS tools seem to take a long time to load up when connecting to the metadata server you may benefit from running a reorg. The %OMABAKUP macro includes a reorg parameter which reduces the amount of fragmentation in how the datasets making up SAS
Waiting on a sas program to complete and troubleshooted the activex graph control errors that you can get when SAS sends you a email with a activex gchart. I went to Outlook and selected Tools -> Options, and changed the Security Zone to Internet (see below).
So you want to add a URL or an email mailto: in that little footnote of your PROC REPORT so people can pester you with more questions? 'Contact Us' But instead of 'Contact Us' the entire string appears: <a href="mailto:bi-weblog@earthlink.net">Contact Us<a/> The Magic?? Add the <div;> </div> tags around the
Ran into some space problems a while back, not like NASA's though. The Work Directory for temporary files just wasn't big enough to handle all the sorting and other processing of the data. Had to do a few things to fix it - and none included buying memory. 1. Review
Attended a DI Studio Overview class today. Just a couple of tidbits for others looking to pick this product up. Using the Propagate tool from the Process Window only propagates items between working tables/processes in the process. Variables that need to be propagated into the target tables need to be
So what do you do when you create metadata that cannot be currently managed via the SAS Management Console? Take for instance the Theme Deployments for the Portal. The standard is alright, but what company wanted their measures all to be printed with the 'SAS Portal' words on the top
So you have installed the SAS System, and you can check what is licensed with the proc setinit command, but what if something hiccuped in the install. Or your supporting (I mean validating) someone else's install and you need to quickly see what is available? Included below is some 'found'
Upgrading your EBI SP4 to DI Studio 3.4 creates the capability of packaging up areas of Metadata (such as the tables in a library) into a "spk" file. Allowing you to then import those items into another repository. This is the FIRST time a GUI driven system has been available
