This could be old information, but setting cardinality in Cognos simply tells Cognos where to expect the measures.  N:N says there are measures on both sides of the join.

N:N seems wrong for two reasons:
It seems unlikely that a Date table would have measures.
It seems unlikely that one Fact row would be associated with many Date rows.

But the cardinality can't be causing your data explosion.  It seems like you've taken a table with 130,000 rows and joined it to a table with about 1300 rows on 1=1 rather than on something like Fact.OrderDate = DateTable.FullDate.

Also, if your data module joins the tables

Quotein the exact same way

as in the dataset, you would get exactly the same results.

Next time you ask for more information about this, please post your data model clearly showing the relationships between all elements and highlight or describe the relationship that you think is causing the problem.

Quote from: dougp on 09 Dec 2025 09:54:38 AMAfter rereading this, I think this is the symptom to focus on.

By any chance, does your date dimension have about 1300 rows?  About 3.6 years?  Of course, working with non-rounded numbers to begin with would help.

I think what you are meaning by N:N is not even that the date table and the fact have a many-to-many relationship.  I think you're saying they have no relationship -- a cross join or cartesian join.  So the result is a dataset with the number of rows being the number or rows from fact times the number of rows from the date dimension.

Creating a proper relationship between the tables will help.  The result should be the number of rows on the fact.  Once you have that, you can start trying to use the dataset to answer questions.

Hey, thanks for your help! I have modelled the tables in a datamodule, using a N:N relationship between FACT_Trajectories and DIM_Dates. Simply plotting FACT_Trajectories on a graph works smoothly. However, when combining it with the DIM_Dates, I get a time out error.

I do not actually combine the two tables into one single table if that is what you mean. However, to plot de data with the two tables combined, I suspect something similar to what a combined table would look like is created in the background. Or is that assumption wrong?

Quote from: bus_pass_man on 09 Dec 2025 09:17:11 AMI don't know what you mean by 'trajectories' and I think I don't need to know, although knowing would be nice.

You want the count of trajectories where start date >= {some date} and end date <= {some other date} is that a correct understanding?  That is easily done, without mucking about with many to many relationships.  Why didn't you try that?

Thanks for your reply! A trajectory is a provided service to a client. A client. However, at any given point in time, one client may be provided multiple services (in other words: a client can be in several trajectories at a given time). For my business case, I want to know the number of unique clients at a given date.

To do this, I make a N:N connection between my FACT_Trajectories and DIM_Dates (since one date can be part of many trajectories, and one trajectory can be part of many dates), and put a count distinct on the client number.

It can't be about order of operation.  Filters in Cognos are combined using AND.  Draw a Venn diagram where each circle represents the data resulting from a single filter.  The intersection of all of the circles is the result of applying all of the filters.  If the results look wrong, it is because your filter is wrong.

I'm working with v11.2.3 and getting unexpected results (result set) in a query with nine Detail Filters.

I've successfully tested each filter alone and get the correct result set each time.  Even when 6, 7, or even 8 Filters are active, the result sets are correct.

But I get wrong result set when all nine Filters are active.  Records which should not be excluded are being excluded even though they were not excluded in earlier tests with fewer than 9 Filters active. 

I am using Minimum and Maximum expressions on separate fields in separate Filters.  Quite literally, it looks like if I could control the other of the execution of one or specific Filters the results might be correct.

Is there anything that I can do inside of a single Query to influence the execution order of my Filters?

Orchestrate can call APIs, run tasks, trigger external systems, and handle conditional logic.
Cognos exposes REST and SDK endpoints for:
- Refreshing packages
- Running reports/jobs
- Checking job status
- Downloading outputs

Has anyone used Orchestrate to connect or pair to Cognos Analytics?
Any tips or tricks?

Here are ten tasks BI teams can automate right now to save time and reduce errors.

- Identifying duplicate reports
- Detecting unused content
- Testing report execution after upgrades
- Tracking security changes
- Validating packages and lineage
- Monitoring dispatcher performance
- Flagging reports that fail or exceed thresholds
- Cleaning orphaned objects
- Logging version changes
- Running scheduled health checks

These tasks consume countless hours across BI teams. AI agents and automation tools help eliminate that burden.
MetaManager and BSP Software tools can help with all of this... Get Your Environment Automated and Under Control

For many BI teams, AI adoption feels overwhelming. A simple modernization roadmap helps break it down. First, stabilize and optimize your existing Cognos environment. Second, upgrade to Cognos 12 to gain the latest security, performance, and cloud aligned capabilities.

Once the foundation is solid, begin layering in AI enhancements such as predictive forecasting, natural language querying, and automated insights from WxBI. The journey from BI to AI is not a leap. It is a series of clear, manageable steps that any Cognos team can take.

Watsonx BI represents the next evolution of analytics for organizations that have relied on Cognos for years. Instead of replacing dashboards or reports, it enhances them by bringing predictive intelligence and natural language capabilities directly into the BI workflow.

For long time Cognos teams, this means analytics can shift from "What happened" to "What will happen" without rebuilding your reporting environment. Watsonx BI sits alongside Cognos and unlocks insights that used to require a data science team. Predictive forecasting, anomaly detection, and automated narrative generation allow BI teams to deliver more value in less time.

Cognos 10.2.2 on Oracle...

in a query, i'm inserting a simple mapping:
case
  when [dimension] = 'value' then 'blah'
  else 'blub'
end
That one works fine. Replacing the syntax with a simple case however:
case [dimension]
  when 'value' then 'blah'
  else 'blub'
end
will fail to run and yield an ORA-12704 character set mismatch. My [dimension] on the db is of type NVARCHAR; the only thing I can think of here is that search case and simple case use different data types for interpreting  the literals - is that what is happening?