Providing software solutions since 1976

• Log in
• Create profile
• Welcome
  [Log out]
• Edit profile
• My SAS

• Print  |
• Feedback  |
• Share

  • E-mail
  

  E-mail This Page

  Your Name:*
  Your E-mail:*
  Recipient E-mail:*
  Send a copy to me
  Personal Message:
  
  

  * indicates a required field

SAS^® 9.2 introduced a new user interface for defining member-level security within a SAS^® OLAP cube. This interface enables you to point and click to define a security condition. If your condition begins the security at a level beyond the first user-defined level in the cube (see below for an example), the generated expression will be incomplete and might result in errors or a traceback in the SAS OLAP Server log.

As an example, consider a dimension named Example, which has the levels, A, B, and C. Security is placed on the first member of the B level, which is A1.B1, granting access to the member and its descendants at the C level. This results in a security condition that looks like this:

   {[Example].[All Example],
    [Example].[All Example].[A1].[B1],
    Descendants([Example].[All Example].[A1].[B1])}

This condition would enable users to access only the All Example member because there is a break between the All Example member and the A1.B1 member. To provide the correct results, you would modify this expression to include the A1 member:

   {[Example].[All Example],
    [Example].[All Example].[A1],
    [Example].[All Example].[A1].[B1],
    Descendants([Example].[All Example].[A1].[B1])} 

The incorrect expression syntax might also cause a failure in the SAS^® OLAP Server. This issue can be resolved by applying the available hot fix for Base SAS 9.21. Click the Hot Fix tab for the download.

Operating System and Release Information

A fix for this issue for Base SAS 9.21 is available at: