Invalid Expression is actually valid

[Tsunami]

I have a report that is one query and it worked fine.  I later had the request to substitued customer ID for customer name.  This require creating a join.    So, I created a new query subject 'Customer' and joined it to Query 1 to create Query 2.  I selected the list and changed the reference to Query 2.  Now everytime I run a report, I get the message [Query1].[Column8] is invalid.

"Column8" in the original query was a conditional 'if then else' expression.  It said if a flag was checked, show a value in another column, else null.

If I run Query 2 to 'View Tabular Data' it seems to work fine, but if I reference Query 2 in my list I get the error mentioned earlier.

I found some documentaion about setting the data property.  I tried that but it didn't seem to help.

Any ideas?  Thanks.

[Lynn]

I have to apologize in advance for responding without having a specific answer to your question. There is a "Properties" property associated with the list level of a list container which may be what you are looking for.

However, my comment is regarding the Framework Manager modeling that was done to support reporting in your environment. Perhaps it is more accurate to say the Framework Manager modeling that WASN'T done.

The fact that you, on the Report Studio side, have to deal with joins as trivial as connecting a customer ID to a name (and you had a similar question the other day regarding personnel ID and name) is an indication that you are not leveraging Cognos to it's potential.

A solid FM model should establish a meta data layer that encompasses the technical aspects of how database objects join together as well as transforming things into business focused subject areas with meaningful names. One sentence alone can't convey the importance of the modeling step, but this gives a glimpse at least.

While some time is involved initially, it pays off in the long run in terms of faster report development, increased accuracy, minimized maintenance, etc.

You may not be in a position to do anything about it, but I felt it was important to point out. I believe there are cases when companies decide they are "unhappy" with Cognos because they had a poor implementation.

[Tsunami]

Thanks Lynn.  I've tried in regards to the properties.  It had no effect.

I'm aware of the modeling deficiency but I'm just working with what I was given.  :-/  The 'model' I was given only has one layer and it consists of multiple views and vague tables.  It's been a headache trying to figure everything out.

I'm a beginner at data modeling but I know when somethings wrong when I see it.  Hopefully I'll be able to get my hands dirty and create a better model.