# Licensed Materials - Property of IBM # IBM Cognos Products: OQP # (C) Copyright IBM Corp. 2005, 2019 # US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM corp. # # OLAP Metadata for OLEDB providers. # # Indicates if we should be faking member keys. This is required for when we have no knowledge of the keys. olap.metadata.fakeMemberKey=true # Indicates if we should be skipping any property that ends in ".MEMBER_KEY". This is needed for Cubing Services, # since we get two MEMBER_KEY properties returned when the customer has modeled it, and we only need one! :) olap.metadata.skipDotMemberKey=false # Indicates if we should be forcing parent-child hierarchies to be treated as unbalanced. olap.metadata.forceParentChildToUnbalanced=false # Indicates if we should be forcing ragged hierarchies to be treated as unbalanced. olap.metadata.forceRaggedToUnbalanced=false # Indicates if we should be returning hierarchies as dimensions. olap.metadata.returnHierarchiesAsDimensions=false # Indicates if we should be using the level names to determine if a hierarchy is parent-child. For MSAS 2000 and # Cubing Services, if all the level names for a hierarchy start with "Level " and a number, then we consider it to # be a parent-child hierarchy. olap.metadata.determineParentChildByLevelNames=false # Indicates if we can use Member Unique Names for the Actions restrictions. # For MSAS 2005+, this is fine. For 2000, when retrieving the Dimension Actions, the # co-ordinate must be a HUN :). For Level Actions, it must be a LUN (not a MUN). olap.metadata.useMUNsForActionRestrictions=true # MDDS doesn't worry about sorting hierarchies for MS2005+. # In order to remain consistent the ODBO provider shouldn't either. olap.metadata.applyNewRankToHierarchies=false # Does this provider support Trusted Connections. olap.connection.supportsTrustedConnections=true # Does this provider support CAM Authentication (SSO). olap.connection.supportsCAMAuthentication=true # Can we use impersonation with the signon supplied? olap.connection.supportsUserImpersonate=true # Can we skip version validation? olap.connection.skipValidateVersions=false # Should we use tabular formatting? olap.data.useTabularFormatter=false