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 Db2
Created by Guest
Created on Nov 29, 2023

Quick Search should trigger a data refresh

Please refer to case TS014307927 for details.

Quick Search on all DMC views does not enforces a new query to either the repository or to the monitored DB.

It only searches on pre-loaded data in the browser , which is not a complete set of data.

For Performance reasons, DMC grids does not load all data to the browser.. It uses pages fashion and data is load as user moves to the next pages to see more data.

The quick search functionality does not enforces a new query, and the searches only happens at the front end pre-loaded data in the browser.
On bigger and production databases , where there is a lot of data sometimes.. (hundreds of pages) , you search for an app handle for example that you are sure it exists, but the tool does not finds it, because it was not present in the 1st initial sub-set of rows that was pre-loaded..

In order to que quick search finds it. the user is forced load "everything" possible by clicking next pages to load all of them, and them perform the search.

This is not what the end user expects to happen, and not the same behavior in mostly similar web tools that offers a search option.

When the user types something in the search box, and hit enter, it's expected that the tool performs a new query to the back-end data, and load just the relevant information the matches the search criteria.

Needed By Yesterday (Let's go already!)