If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Cascade Prompt

Started by amoslade, 04 Aug 2021 02:41:47 PM

Previous topic - Next topic

amoslade

We are in the process of an upgrade and going from Cognos 10.2.1 to 11.1.7.  We have reports that were created in 10.2.1 with cascade prompts that are not functioning in 11.1.7.  Is there a known issue with this?

amoslade

I found an answer to this.  Apparently this is specific to Infor EAM and how reports are saved.  EAM uses Cognos as a built in feature for report writing.  Infor EAM 11.3 and Cognos 10.2.1.  When you see the XML of the report in 11.3 it says "<modelPath>/content/package[@name='InforEAMPackage_113']"  Apparently when that was converted, due to changes IBM made in how Cascade Prompts work, the prompts failed.  I simply changed the '3' in InforEAMPackage_113 to InforEAMPackage_11x and it functions correctly.  Sorry if this should not have been posted here.  I thought the issue was Cognos related at first.

MFGF

Quote from: amoslade on 05 Aug 2021 08:23:51 AM
I found an answer to this.  Apparently this is specific to Infor EAM and how reports are saved.  EAM uses Cognos as a built in feature for report writing.  Infor EAM 11.3 and Cognos 10.2.1.  When you see the XML of the report in 11.3 it says "<modelPath>/content/package[@name='InforEAMPackage_113']"  Apparently when that was converted, due to changes IBM made in how Cascade Prompts work, the prompts failed.  I simply changed the '3' in InforEAMPackage_113 to InforEAMPackage_11x and it functions correctly.  Sorry if this should not have been posted here.  I thought the issue was Cognos related at first.

It's an interesting post, and definitely worth documenting online here, in case others run into the same issue. Generally, IBM has a policy of "No report gets left behind" when upgrading from 10.x to 11.x, meaning all reports should work in 11.x exactly as they did in 10.x. In view of that, I suppose it makes sense that this was an Infor issue, although it's a little worrying you have to hack the report XML to fix it.

Thanks for sharing!

Cheers!

MF.
Meep!