Skip to Main Content
IBM Data and AI Ideas Portal for Customers

This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Data & AI Roadmaps ( - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at

Status Future consideration
Workspace Cognos Analytics
Components Administration
Created by Guest
Created on Oct 9, 2021

Remove the need for NC Drop, handle dead processes / schedules better

Currently, if a bad report is scheduled or something happens to the environment, the NC table can build up as explained by this technote and make schedules slow or send them into pending. To resolve this requires a lengthy process of a) backing up the content store (requires DBA, takes hours) and b) running the NC drop script. Please build this into the system and prevent this table from building up. It's going to happen, and shouldn't be something you require customers to do. The system should be handling cleanup on it's own and not require your customers to overengineer their own processes to make up for the system not being resilient.

Cognos is a product that has been around a long time and is likely in a fairly mature state at most enterprises. Given this, it is likely a lot of projects have been created over time that aren't what we would call "perfect" -- that means things like using old features, using CQM, multiple versions of the same report copied by users over time, i.e. not best practices, using messy direct SQL. It is one thing to have to treat your Cognos environment very militantly to prevent this from happening, i.e. restrict access, increase testing costs, overtune the environment, spend large on training, etc. This is fantasy though and is probably unachievable in some of these legacy environments where the Cognos expertise is low.

Needed By Yesterday (Let's go already!)