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

Issue in Cognos 8.4 with IN statement?

Started by martin, 06 Jul 2011 04:46:10 AM

Previous topic - Next topic

martin

We have recently installed Cognos 8.4 and now we are having some issues in Report Studio when using an IN statement in the filter. The content store was automatically updated from our previous 8.2 installation. It looks like everything is working except when a report uses an IN statement. For example if we use this filter in a query: [Data Item1] in (10; 11;12) is not working, but if we change the filter in [Package1.Data.Items] in (10;11;12) it works.

So if we are not using the full path in the query we get this error:
QE-DEF-0261 RQP - Parsing text:...., RQP-DEF-0149 The query specification is incorrect.RQP-DEF-0457 Referenced Query....not defined or its query items contain unresolved references.

Is there any body who knows the solution for this problem?

Thanks in advance for your time.

MFGF

This is probably a silly question (I'm famous for asking them! :) ) but do you have [Data Item1] already defined as an item in your query?

MF.
Meep!

martin

#2
The data items are defined in the report (query) and the report worked fine in Cognos 8.2. We think that this is an issue which occurs when upgrading Cognos 8.2 to 8.4. Probably if upgraded to 8.3 first and then upgraded to 8.4 this problem would not have occured, we think... An other thing is that we haven't installed the lates fixpacks...8.4.1 and 8.4.2. So we are still trying to fix this problem...

martin

Found the solution for this problem with help the help of our implemention partner! The language of our packages in Cognos 8.2 were set to English, but were developed in Dutch. This was no problem in 8.2. In Cognos 8.4 this is not working and in 8.4 the language of the packages needs to be the same language as in wich the packages were developed. Also if a package has been developed in the Dutch language you cannot work with "," instead you must use ";" so we need to modify all our reports. I'm not really happy with the extra work this requires, but I can live with solution.

MFGF

Meep!