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 Employees should enter Ideas at

Status Submitted
Workspace Cognos Analytics
Components Reporting
Created by Guest
Created on May 2, 2024

Improvement to Report Bursting: Recover from a fail, better error reporting

When bursting a report it is difficult to work out which parts of the burst have been successful or not.

After a burst Cognos should be able to tell you which burst keys were successfully burst and if any emails were sent. It should also be able to say which burst keys failed to create a burst or failed to email. This would allow administrators to easily identify out of a lerge burst who has or hasnt received an output.

Bursting should also have some method of rerunning for failed burst keys. An administrator could fix the issue, but how do they send the output to the people who have nor received an output.

For example. A burst is run overnight, it is meant to burst a report output to 2000 people.

In the morning the administrator logs in and from the error log sees that some parts of the burst report have failed. Currently they cannot easily identify out of the 2000 users who have or havent received the report. They also cannot easily rerun the report and just send the output to people who havent received it.

With better functionality...

The administrator gets a report at the end of the burst saying which outputs were sent to users. They also see which burst keys failed.

The administrator takes corrective actions.

The administrator uses the "rerun for missing burst keys option" from last nights run.

This reruns the burst, but only for keys that failed.

The administrator can repeat these steps until all outputs have been sent.

Needed By Yesterday (Let's go already!)