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'.
As I have previously mentioned, SAS 9.3 has some sweet new functionality for stored processes. The topic of the prior post was on storing .sas code for the stored process directly within the metadata and how to edit/access that raw code. Did you know that the 'Edit Source Code' button
I mentioned back in 2008 that Web Reports with OLAP source can drill-through to detail (or display the raw data records for the corresponding cross tabular cell) only after the source information map has drill-through to detail enabled. Well, there are several other areas that also could disable this capability
In BI Dashboard 4.3, you have the ability to edit or entirely remove the frame around an indicator. When in the dashboard edit screen, select the indicator and on the right hand side update the Object name with the frame title to display. When viewing this indicator from the Portal
Co-written with Gordon Cox@gtcox76 Gordon’s 7-yr daughter asked him what he learned in class at SAS Campus a few weeks ago. The subject, even for many SAS geeks like us, can be hard to tackle. Gordon was learning all about SAS GRID architecture, implementations, and usage. Well try to explain
New in 9.3, stored processes can be assigned to run on the 'Default Server' server type. Developers can still force the stored process to run on only one server type but choosing the 'Default Server' allows the client application to specifically call the best server type to run on. Another cool
There is some sweet new functionality in 9.3 stored processes. One of them I particularly like is the additional option to store the SAS code within the metadata rather than in a separate .sas file. This is extremely beneficial when allowing the stored process to run on multiple application servers. It also could
Chris mentions in his FAQ post on 9.3 and Enterprise Guide that the new stored processes and other new metadata can not leverage all of the functionality in the new 9.3 release. EG is nice to remind us of that fact when we open the SAS Folders view with the
According to the SAS Documentation http://support.sas.com/resources/thirdpartysupport/v92m3/browsers.html Windows 7 machines should use Internet Explorer 8. Unfortunately Microsoft will no longer allow installations of IE 8 on Windows 7 machines. http://windows.microsoft.com/en-US/internet-explorer/downloads/ie-8 I was able to get all the web applications to work on Google Chrome however the BI Dashboard appears but not all
Just got some time to begin playing with the 9.3 Enterprise Business Intelligence installation on my SAS laptop. As I was testing out the web applications, SASWebDoc opened but I couldn't get to the SAS login screen up to access the SAS Stored Process web application. First I started perusing my
Creating shared prompts to use across the various BI clients requires the use of SAS Management Console's stored process wizard. Editing these prompts after they have been shared requires some forethought. The important thing to consider when making any changes to a prompt's properties is the impact these changes could
