I have been tasked with converting a number of old CDD reports to Cognos Analytics (11.1.7). The process has gone well so far, except for image drill downs. I've found the data in the im_ files (im_page, im_index_data, im_info, im_index_mstr, im_index_dtl) but trying to roll my own solution from that seems kludgy and overly complicated.

How does one go about reproducing the image drill down functionality in 11.1.7?

Any help/guidance would be greatly appreciated.

I've found a 3-step solution

1.   Reverse = reverse([String_Column])
2.   ParseReverse = substring([Reverse], 1, position(' ', [Reverse])-1)
3.   ReverseParseReverse = reverse([ParseReverse])

It's a bit long-winded but it works.

e.g. If the text read 'AAAA 12345 BBBB CCCC' I'd like to create a column that shows 'CCCC'.

Hi all,

I have a string column with varying lengths of text and varying numbers of spaces.  I'd like to isolate the text following the last space at the end of the string.  Any ideas about how I can do that?

Thanks,

Cogency

Quote from: Eric.Pleiss on 15 May 2025 09:48:14 AMThe MetaManager software allows easy access to user my folders and content, and as an admin you should be able to quickly diagnose the underlying issue, or just delete them for the users as a sys Admin. 

Thanks, Eric. We have MetaManager installed at work. I'll look into that.

Hi everyone,

I recently migrated a Cognos report from Cognos 10 to Cognos 11 and I found an issue with the way Excel handles merged cells in a list.

Each column in the list has two data items, with the second item being in a block. In Cognos 10, if Column 1 is empty, only the value of Column 2 will appear in a single cell when exporting to Excel. But in Cognos 11, even if Column 1 is empty, an extra empty cell will be created and merged with the adjacent column.5

Has anyone else encountered this issue? Do you know how to fix it so that the Excel export works as before?

Thanks in advance!

Michael,
You noted "users" above, rather than just a single user, so it seems unlikely that there is a specific corrupted object. 

The MetaManager software allows easy access to user my folders and content, and as an admin you should be able to quickly diagnose the underlying issue, or just delete them for the users as a sys Admin. 

You can download and trial MM for free, and during the trial period you could quickly handle this task.  https://www.bspsoftware.com/products/metamanager/#mm-download

I shot you an email with some more details.

This topic has been moved to Reporting.

https://www.cognoise.com/index.php?topic=38368.0

This topic has been moved to Reporting.

https://www.cognoise.com/index.php?topic=38362.0

Quote from: cogdevadmin1937 on 17 Apr 2025 10:52:03 AMHello,

I have a report I need to re-create in Cognos Analytics from Excel, that uses a TM1 cube as a data source. Hopefully the screen shot I've included help explain things to the fullest.

I'm running into an issue because the report is going to use 4 different hierarchies within the Time dimension, all with different MUN's. The requirement is the user will choose a Month and Year from a value prompt, take March 2025 for example, and March 2025 needs to be passed to the 4 different hierarchies within the Time dimension. If the user chose April 2024 in the value prompt, April 2024 would need to be passed to the different hierarchies, etc./etc.

Is is possible to create these MUN's in the screen shot based off the value prompt selection?

Thank You in advance.

Mike

Hi,

It depends what your prompt is returning. If it's a full MUN from a different hierarchy, you would have some work to do in order to strip out the relevant Month and Year to insert into new MUNS. If it's returning string values for Month and Year, it would be fairly straightforward to insert these into the MUNs you require. All of this would be done within macros in items in the report, and it would make sense for each macro to reference the parameter(s) for month and year using prompt macros. Most of the MUN would be literal values around this, eg

#'[Income Statement New].[Time].[Time]->[TMR].[Time].[Time].[' + prompt('YearMonthParameter','token','202503') + ' QTD]'#

In the above, the prompt macro references the parameter as the first argument (so use whatever parameter name you need), the data type returned as the second argument, and a default value for the parameter as the third argument.

Hope this gives you a nudge in the right direction.

Cheers!

MF.