Use List for relational model, Crosstab for dimensional model.
This means that if you are using Cognos in a real data warehouse scenario you can most certainly forget about lists.
The good news:
- Everything you can do with list can be done with crosstab (so you won't miss it)
including having only one dimension - if you can get it working in crosstab then you can plot it on a graph
graphs work exactly like crosstabs
Posts
I think that you're grossly oversimplifying this.
ReplyDeleteFor one, Cognos and crosstabs are an unhappy couple. This is probably not even a Cognos issue, but rendering a crosstab in HTML draws all resources for anything bigger than a couple of pages. The reason is that Cognos probably needs to calculate ALL the intersections to come up with the first page. The second culprit is specifying the width of data displayed. This is MUCH harder to achieve because of the dynamic nature of a crosstab. In all reality HTML simply does it's own thing regardless of the sizing specified. A third issue involves displaying non-numeric data in the body. Cognos appears to accept only facts with aggregations set as a body-component. This is pretty disappointing for building reports that are meant to display time-based developments.