Cognos BI

Bursting Gotcha

After spending what seems like ages trying to troubleshoot why an account does not have access to burst a report, I thought I’d share the solution. In addition to setting up the capability for a user to burst content, this is also a capability at the package level. Duh.

read more

TM1 Server Crash Notification via Event Viewer Scheduled Tasks

TM1 Server Crash Notification via Event Viewer Scheduled Tasks

I’ve just put together an XML query that filters the event viewer to just show TM1 application crashes. This can be used as a custom view in Event Viewer to see all TM1 application crashes, and it can be into a scheduled task to take other action, such as sending an email to interested developers, or maybe even restarting the service.

read more

Find who’s been tampering in the content store

Today I was poking around in Production and noticed the modified date on a report of yesterday. After asking around my team, it became apparent that none of us had made the change… was there a security hole? This query allowed me to identify who made the change… and as it turns out the modified date can be updated by quite a few scenarios in Cognos, including any user creating a view in their My Folders. Oh well, here’s the query for next time!

read more

Cognos BI Instance on Analytics Zone

Cognos BI Instance on Analytics Zone

Just putting this here as I had to spend 30 minutes finding the link: http://cognos10.analyticszone.com/ibmcognos This is quite a handy resource – here you can log into a hosted environment of the very latest Cognos verion. Perfect for checking out what’s coming, and evaluating new features without the overhead of finding, downloading, installing, and configuring the latest version of Cognos BI.

read more

Using Cognos 10.2 Prompt API to create a multi-select popup prompt

When clicked, this pops up

This solution uses javascript, cascading style sheets and the prompt API to neatly provide a multi-select control that doesn’t use a lot of screen real estate I’ve put together a fully working example against the GOSales (query) package, click the download icon below to get the complete package: There are a few pieces required to make this all work: A CSS script – popup_multi_AM.css A Javascript file – popup_multi_AM.js Five HTML items A text box prompt A list box prompt An image – DropDownPlus.png Note that all of the examples below are hard coded for a ‘Product’ control. popup_multi_AM.css popup_multi_AM.js popup_multi_HTML_Initialise popup_multi_HTML_1 popup_multi_HTML_2 popup_multi_HTML_3 popup_multi_HTML_4 Text Box prompt This control must have the ‘Name’ property set to ‘prDisplayProduct’ List Box prompt This control must have the ‘Name’ property set to ‘prProduct’. DropDownPlus.png Report Studio Layout

read more

Seaching Cognos 10 Content Store for an XML string

Seaching Cognos 10 Content Store for an XML string

We recently migrated our knowledgebase from Collab to sharepoint, which meant all reports that had links to collab needed to be identified and edited. This query proved helpful – it searches the content store for occurrences of the old string, ‘collaboration.au’, and displays the report name and location. The query does take a while to run though – almost 40 minutes against our beast-mode content store…

read more

Auto-Generated prompts in Cognos 10 BI

Auto-Generated prompts in Cognos 10 BI

I had an issue with Cognos 10 today whereby the automatically generated prompt control for a BI report was showing a drop down list, rather than a type in prompt. The reason this was an issue is that I wanted to set up a schedule of this report, with this particular prompt being for ‘Client Code’. As we have many thousands of clients, there seems to be a limitation with auto-generated drop down prompts whereby they only showing the first thousand or so records. After some experimenting, I was able to find that coalescing the column with a null string would force the auto-generated prompt to be a type-in box, thus allowing the client code to be entered. Here is the code originally used by my filter: #/* Strategic Client */# [Engagement Revenue].[Strategic Client Level Dimension].[cons_client_cd] = ?pStrategicClient2? and here is the modified code that uses a type-in prompt box: #/* Strategic Client */# coalesce ([Engagement Revenue].[Strategic Client Level Dimension].[cons_client_cd], ”) = ?pStrategicClient? Below is a picture showing both these prompt behaviours: Note: I’ve since discovered you can also set the prompt behaviour in the Framework Package

read more