Was doing some development with Information Map studio today, developing a map on top of a SAS OLAP Cube.
Went into preview mode to test the map and double clicked on a tile and wahoo it drilled down the dimensions hierarchy.
Didn’t know you could do that, learn something new everyday!
Been struggling with how to trap a divide by zero issue’s in SPM formulas, so we don’t show the dreaded NULL value.
With a little help from SAS support, finally worked out what I need is:
IF((/100))
So basically if the dividing calculation results in an error (i.e one of the dividers is 0 or missing) then put a 0, otherwise do the calc.
If you have ever wondered if there is a limit to the size of a SAS 9.1 OLAP cube, then there is and it is documented on the SAS Support site underSAS 9.1 OLAP Cube Size Specifications.
According to SAS 9.2 OLAP Cube Size Specifications limitations also exist in 9.2.
10 points if you can tell me if it has changed in 9.2?
Been doing some work on SAS Security lately and the post over on Angela Halls blog about Managing Metadata via EG, elicited my post. Particluary the comment “NOTE:: Deleting Metadata can cause orphan content elsewhere, so use this capability judiciously.”
When you first install SAS it by default optimistic, by that I mean it allows public, and SAS Users to do lots unless you stop them.
Now if you do the SAS Administrators course the first thing you get told is to secure metadata, i.e change it to a pessimistic view, where users can’t do anything unless you grant them (or a group they belong to) rights to do so.
Easier said than done, as you can’t just deny everything to Public and SAS Users as nothing will work (because they need to be able to read and write metadata to check what they can do 
So you need to play with your ACT and Group structure to initially deny them everything and then grant access to what you want them to see.
I suggest you at least deny the write metadata on anything you want to keep, before you show them in Enterprise Guide how to delete stuff
I beleive this all changes in SAS 9.2.
I was looking for the latest user guide for SPM 2.4 and clicked in the link here on the SAS Support site and got the message:
"SAS Software Documentation
Documentation for this product is available for customers only. Please contact SAS for details about accessing this documentation.
See your product HELP system for additional information. "
Over on the SAS Support site.
http://support.sas.com/documentation/onlinedoc/spm/
(thanks to the friendly Presales dudes for the pointer)
So ever wanted to know where the Period values iN SPM are actually stored?
Well as long as you aren’t trying to do some dodgy updates to the SPM schema, as you know that is against the rules…
The first trick is that Periods are stored in the SAS Solution Data Mart layer not in SPM itself.
They are stored as a master details record with:
Of course as I have said don’t touch these manually and you should really use the prebuilt SAS Time view to look at them
I read a few blogs off and on when I get time.
Over Easter I have been trying to catch up (as well as doing some paid work, which involves a lot of use of Enterprise Guide, man I love that product) and stumbled across this blog from Jim Dononvan.
What caught my eye was this graphic:
I have to say over the last 15 years I have been very lucky to have jobs that fit the sweet spot (and pay not to badly as well)
Is your current job in the sweet spot?
If not whats stopping you from changing it?
Following on from developing our MediaWiki plugin that dynamically exposes SAS Metadata within the Wiki, I have been researching whether we should build a Microsoft Sharepoint Web Part to enable customers to stream SAS Metadata dynamically within Sharepoint.
I came across this paper “Paper 390-2009: Henderson, David; Alexandre, Sean - Integrating SAS® Business Intelligence with Microsoft SharePoint” from SAS Forum 2009, that outlines how SAS provides integrations/web parts for BI Dashboards and Stored processes already.
Cool!
In SAS eBI 9.1 and 9.2 there is no easy way to migrate Portal pages across SAS instances.
So if you follow what we call Optimal practice and do all development in a separate SAS Development environment, then promote it to a UAT environment and finally to Production, there is a lot of rework instore.
We were thinking about creating a sasInct module to assist in this task but thanks to a tip off (thanks Robin) we have found out that SAS are about to release a utility that enables you to migrate portal pages on both 9.1 and 9.2.
It is due in the next couple of weeks, so ask your friendly SAS Account Manager or Presales Dude/Dudette.
Once I have tested it I will let you know what I think.
So looking for some help from the SAS community.
On a project we have focused on delivering content via Web Report Studio and Infomaps.
We now want to allow users to access the content via Office Addin and Enterprise Guide.
But (there is always a butt we only want users to access data via Information Map, we don’t want them to access the base libnames or tables.
Why you ask, because we have all the business rules embedded in the Information Maps so we don’t want users bypassing these and defining there own business rules on the base data.
Of course if we deny access to the libname then the Infomaps will fail. We can’t restrict access to all data types (i.e tables) in AMO or EG.
So any ideas out there?
Things we are going to try:
But we are pretty sure that neither of these will work.
As the title says, Help!
Recent Comments