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'.
Well, setting up a SAS Installation Depot is one thing, but how then do you get users to install the SAS Add-in to Microsoft Office. After attempting to point them to the directory … root folder\client9cd\msofficeint\setup.exe some of my users received error messages such as: COM object with CLSID {C97B3405-B0CA-4B1A-9B90-C334554D81BC}
There has been a lot of confusion at my company on what all of these different products from SAS are about. However, during a training session yesterday I was able to convey the variations of the SAS products by creating an analogy with Television stations and products. This gave the
MS Excel limits cells to 910 characters in length. The next version of SAS Add-In to Microsoft Office (AMO) addresses this issue by truncating records & giving the user a warning message, however what do you do with users today? Answer: Truncate the format & informat in a SAS Data
So you modified the SAS EG character formatted constraints to resolve automatically with surrounding single-quotes. (Seen below from Stored Process Wizard and Management Console screens.) Of course, the pain now is trying to pass dynamic parameters through the %stpbegin & %stpend statements.
If you need to give your users the ability to select multiple OR no values within a selection box, the stored process needs to be capable of addressing this flexibility. For the example below, users wanted to choose 0 to 3 severities (of 4) to exclude from the results. %macro
Problems connecting to the SAS OLAP Server in MS EXCEL after downloading ONLY the SAS OLAP Data Provider on a virgin SAS Machine? When installing the SAS OLAP Data Provider for use in MS Excel Pivot Tables, be sure to use the Integrated Technologies for Windows download, rather than the
MDX has a limit to the length of values used to query. Therefore, all OLAP data must maintain a format less than 256 characters in length. You can follow the steps below to reduce the size during PROC OLAP creation (using OLAP Cube Studio) and then regeneration using the PROC
Even as stated in current SAS OLAP training sessions, refreshing OLAP Cubes doesn't work as documented. Problems arise when specifying special options for formats (like reducing from $300. to less than the maximum $256.) since these are not stored in the saved PROC OLAP code. Also, if you run the
