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

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:

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

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Functionality already exists
Created by Guest
Created on Jan 9, 2019

Allow custom IDs for documents when adding them to the discovery index

Whenever we face discovery setups with multiple stages or environments, its very hard and time consuming to manage multiple copies of the same document as discovery generates a new, different ID for each document in each collection. It would make things much easier and faster If one has the ability to provide a custom Id when uploading the documents. This way, they can be easily linked and copied or stored in a backup.


Problem: Currently its only possible to upload documents with custom IDs by using the update function on a non-existing document ID which equals the intended custom ID.

Expected behavior: Updating a non-existing document fails.

Observed behavior: A new document gets created with custom ID.

This doesn't make sense at all because you should not able to create documents via the update function and if, the add route should provide at least the same functionality, i.e. adding documents with custom IDs (e.g. using an optional parameter).

  • Guest
    May 3, 2019

    The feature as requested "Allow custom IDs for documents when adding them to the index" is already available, as you mentioned using the Update API.  It sounds like you have some exception with our API semantics (that update shouldn't create new).