Tej, If they are Web Report Report Creators, they can save the report to their personal folder. (Still lock them out of the standard template/report - so they dont wipe out the standard view - using Deny WriteMetadata.) However from IDP, they would need a personal collection portlet to link directly to their report. As this is now saved outside of the standard template location the first link you supplied would just take them back to the original view. There are probably some more customized solutions you could build to do this - such as a custom portlet - that would search for reports with certain names in their personal folder and link to them directly. ~ Angela ... View more

Changing metadata security on individual objects could prove to be a cumbersome security management strategy. What BIC_USER_3 points to is that there is a problem with your security levels, and changing them will address this. However take a look at your overall security structure so that this same issue is fixed across the board. 1. Consider assigning all the portal users to the User Manager Role 'Web Report Viewer'. This way they have no edit capabilities to any reports. 2. If users need the ability to create their own reports in Web Report Studio. Organize the SAS Folder structure in such a way where a ReadMetadata is Granted and WriteMetadata is denied. And Grant/Deny these permissions to groups of users. (So create a group in User Manager for 'Portal Report Viewers' and one for the authors 'Portal Report Editors' - and assign Deny WriteMetadata to the viewer community.) The security administration documentation (http://support.sas.com/documentation/cdl/en/bisecag/61133/HTML/default/titlepage.htm) provides details on how to accomplish this and plenty of reading on how to secure other areas of your system. ~ Angela ... View more

This sounds like a situation where using a stored process with your custom proc sql mdx code would be appropriate. You could then setup the information map to access it and define the table for your Web Report Studio users. My #SASTalks webinar on Thursday last week covered how to do this for switching a query on an RDBMS - but the method would be the same in this case. ~ Angela ... View more

Included are some examples from Microsoft: http://msdn.microsoft.com/en-us/library/ms144821.aspx Your examples below appear to be at a higher level than what the documentation states - you will need to select an individual member. Example: [SalesDimension].[SalesHierarchy].[Region].[State].[City].Properties('AliasName') If you still get the error message in Information Map Studio you can choose to move forward anyway. I would then suggest grabbing the MDX code from the IMap Test Screen and testing in Base/EG. ~ Angela ... View more

If this is a Windows 32-bit machine, you are limited to 2GB per process. Windows 64-bit can be set higher (this is defined in the sasv9_olapserver.cfg file (Windows) or OLAPServer.sh file (Unix)) and might allow for enough space to generate the result. The important item to note is that queries against cubes with high cardinality levels (such as your >15k customer list) can result in a large memory usage. You might want to add a hierarchical structure in the customer dimension to reduce the cardinality - such as having the 1st level in the hierarchy = the alphabet. ~ Angela ... View more

Sorry for the delay Bob. The last couple weeks have been crazy. Are you still working on this item? My guess is that there is an issue with dynamically assigning the SASIOIME library. Could you try to add an library assignment path before your PROC OLAP code (or include it in the Cube Creation GUI: on the first screen for creating/edit the cube, click 'Advanced' and move to 'Submit SAS Code' tab). Included is the meta libref: libname LibID meta liburi="SASLibrary?@name='LibIM'"; Included is a reference on methods to preassign libraries for OLAP Server: http://support.sas.com/kb/12/215.html ~ Angela ... View more

The SCD loader in DI Studio actually builds the dimension table for you. If you already have this table built, then you should be able to add it as a dimension table in your OLAP Cube. You will then need to add a table option for this table with a WHERE clause that analyzes the valid_from - valid_to fields in your dimension table. When you get to the dimension designer screen, after selecting the slowly changing dimension table you will need to include a table option to retrieve only the current valid members. This will then appear in the source PROC OLAP code as an example: DIMENSION test CAPTION = 'test' SORT_ORDER = ASCENDING DIMTBL = sashelp2.PRDSAL2(where valid_from <= datetime() <= valid_to) DIMKEY = MONTH FACTKEY = MONTH HIERARCHIES = ( test ) /* HIERARCHIES */; Hope this helps. ~ Angela ... View more

Awesome news! Thanks for letting me know! Sounds like the start of a great SAS User Group paper! ~ Angela ... View more

For Stored Processes viewed in Portal, I would recommend building a prompt window from scratch. You will have more flexibility for styles and layout. 'from scratch' - can be done in a variety of ways: 1. web page HTML form (Portal would point to the .htm/.html page) 2. Stored Process html form code - http://support.sas.com/kb/37/050.html (portal would point to the stored process) 3. Custom Input Form - http://support.sas.com/kb/38/621.html (portal would continue to point to your current stored process view where this custom input form would be presented.) ~ Angela ... View more

For #2 - check out the Slowly Changing Dimension (SCD). SAS Paper: http://www2.sas.com/proceedings/sugi29/114-29.pdf provides information on how this works, which types (1,2,3). ~ Angela ... View more

There is documentation on how to generate Web Reports outside of Web Report Studio. This might get you started. http://support.sas.com/documentation/cdl/en/biwaag/63149/HTML/default/viewer.htm#a003182446.htm ~ Angela ... View more

It sounds as if the security settings for the library & or table/view are not setup to allow access for drill-through. Read through the SAS Documentation "Security for Drill-Through Tables" found on page: http://support.sas.com/documentation/cdl/en/olapug/59574/HTML/default/viewer.htm#a003212372.htm ~ Angela ... View more

Included is my blog post on how to make user-defined formats available to InfoMap Studio. http://sas-bi.blogspot.com/2010/01/using-custom-formats-in-information-map.html ~ Angela ... View more

You might consider using Identity Driven Security. Reference material: http://support.sas.com/documentation/cdl/en/olapug/59574/HTML/default/viewer.htm#a003212399.htm http://support.sas.com/documentation/cdl/en/olapug/59574/HTML/default/viewer.htm#a003212372.htm#a003212373 and pg66 http://support.sas.com/documentation/cdl/en/bisecag/61133/PDF/default/bisecag.pdf ~ Angela ... View more

If you are interested, Add-in to MS Office provides this type of capability. Included is the KB entry: http://support.sas.com/kb/32/009.html ~ Angela ... View more