- Order misplaced when using union ( version 10.1.1)
- Not Fact related Query ( version 10.1.1)
- Not database related Query ( version 10.1.1)
Order misplaced when using unionWhen there are multiple queries unions, such as different period’s union together for crosstab, YTD, HTD, current Month, last month and etc. the sequence of query items can be misplaced. Cognos doesn’t check the query item name, as long as total number of items and type of correspondent item match.
Please see screenshot below
Obviously, query item region and product line are misplaced.
Not Fact related QuerySometimes, for whatever reasons, all query items in a query don’t relate with a fact table. Even there are some measures, but these measures are defined as fixed value. Please see sample below
This design could cause many not projectable issues, dependant on framework manager. The solution is to have a clear join path defined by adding filters.
Not database related QueryPlease see query below, it doesn’t work
The reason is that the query doesn’t associate with database; it can only work when the function is from Cognos, which uses local processing
The solution is to either use local processing function, or add database related filter