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

namespace fail

Started by dougp, 21 Apr 2022 02:05:38 PM

Previous topic - Next topic

dougp

Not a question, just FYI because this was so mysterious and took me hours to figure out.

tl;dr
Don't name a query the same as a query subject in your source package, data module, etc.



Using CA 11.1.7IF8

I'm creating a report about signs along the highway.

I created a data module that uses a data source defined in Manage | Data server connections and used it in a report.  I also included a few other sources.
In the report, I created a query with the same name (signs) as a query subject in the data module.
I joined this to a couple other queries (partly because I was performing complex calculations and needed to control aggregation, and partly because the data module editor won't allow compound relationships, as far as I know).
A couple queries downstream, I joined it all together and was informed that QueryA, signs, and signs0 can't be cross joined.  Oddly, Query0 didn't exist.  And QueryA and signs were joined properly.
Of course, with this kind of failure Cognos won't display the SQL that is causing the problem.  That would make troubleshooting too easy.
Digging into the Cognos SQL of an upstream query, I discovered that one of the CTEs was named signs0 , but it was well upstream of the actual query and not directly used.

The reference appeared to be because Cognos could not distinguish between [signs] (the query) and [M1].[MySignsDatabase].[signs] (the reference from the source).

Renamed my query = "sign".  Problem solved.