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 Planned for future release
Created by Guest
Created on Dec 21, 2022

Publish Assets from WKC to Watson Studio consistently

Follwing the idea, that data assets have been added and documented in WKC and then pushed to projects that need this data assets, there is a great gap in functionality: when pushing an asset a second (or third...) time to a project, e.g. after the asset has been changed or even only after documentation has changed, this assets gets created again in that that project, using the same name. The only way to identify the assets is by date afterwards. Of course the asset has a different id, so existing notebooks etc. will continue to work - which is good.

A better way of updating an assets has to be found, a user should have the opportunity to decide wether to override an asset, create a new asset (with a new new name), or will just allow to update metadata. BTW: when working the other way round: starting in WS and pushing assets to the catalog, this is already possible!!

Needed By Month
  • Admin
    Susanna Tai
    Jan 17, 2023

    Hi Marc, thanks for submitting the idea. The requirement to prevent duplicate assets in projects is already on the roadmap. I need to confirm the ETA from dev, but the original target was 4.7.


    Susanna Tai