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 Submitted
Workspace Watson Assistant
Created by Deleted user
Created on Feb 25, 2019

Add handling of carriage character

The API currently does not support handling of carriage character. While our UI does handle this, in cases where customers copy/paste data, we are unable to handle unless we build a custom handler to remove carriage characters. While we can implement this on our end, I think that if IBM implement this on the API end, then this will solve this for all customers as this is a global issue. 

  • Guest
    Mar 18, 2019

    This sounds like the ond "LF" vs. "CR/LF" issue.  I would strongly suggest that we use something agnostic (like regular expressions) for API inputs.  So in that case, "\n" would be a line terminator, "\t" would be a tab, and so on.  Otherwise, you get into trouble because often the calling platform is merely the platform that the orchestration engine is running on, and not the platform being used for the UI.

  • Guest
    Feb 27, 2019

    This AHA Request was created by my customer, Quicken Loans