Description:
This document describes how to create a Time Dimension in Framework Manager which is similar to a Time Dimension created in Powerplay Transformer.
Steps:
cast(extract ( year, [
cast(extract ( month, [
cast(extract ( day, [
Note:
‘cast’ function has to be used to convert a numeric field to a string as _memberCaption Role cannot be numeric.
Description:
This document describes how to make Custom User Properties for LDAP available to Cognos 8 Components.
Environment:
- Cognos 8 BI
- LDAP or Active Directory Authentication Source
Solution:
You can use arbitrary user attributes from your LDAP authentication provider (ADS as well) in Cognos 8 components. To configure this, you must add these attributes as custom properties for the LDAP namespace. The custom properties are available as session parameters through Framework Manager.
Steps:
- On every computer where Content Manager is installed open Cognos Configuration
- In the Explorer window, under Security, Authentication, click the LDAP namespace.
- In the Properties window, click in the Value column for Custom properties and click the Edit button.
- In the Value – Custom properties window, click Add.
- Click the Name column, and enter the name you want Cognos 8 components to use for the session parameter.
- Click the Value column, and enter the name of the account parameter in your LDAP authentication provider.
- Repeat the preceding two steps for each custom parameter.
Example for using the NT User ID:
Name Value ntUserDomainId ntUserDomainId
- Click OK.
- From the File menu, click Save.
- Restart the Cognos 8 Service
- Open your Framework Manager Project
- Edit the Query Subject Definition
- Click the Filters tab
- Click Add to Insert a Filter
- Click the Parameters tab
- The new Session Parameter is called $account.parameters.<Name>, e.g.: #$account.parameters.ntUserDomainId#
Example for such a filter:
[Namespace].[QuerySubject].[NTUserID] = #sq($account.parameters.ntUserDomainId)#
Description:
How to create optional prompts in Framework Manager.
Environment:
Windows [ALL]
Solution:
How you create a filter in Framework Manager will depend on whether the filter is seen by a user in Query Studio and or Report Studio.
Here is the expected behaviour seen in Query Studio based on a particular filter
Filter using prompt Macro
E.g. [database].[query subject].[query item] like #prompt(‘Prompt name’, ‘Datatype’)#
Because the example uses a macro filter in Framework Manager, then the filter is required and will be seen in Query Studio.
Filter using ? ?
E.g. [database].[query subject].[query item] like ?QueryItem?
To make this filter prompt optional you need to set the “Usage” as optional in Framework manager.
When you then use this query item in Query Studio you will not be prompted for a value. Please note that this is not the case in Report Studio. In Report Studio, you will be prompted for a value, however, as the filter is optional, the user can press the OK button without selecting any data items.