Skip to Main Content
IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform 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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - 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 https://ideas.ibm.com



Status Under review
Workspace DataStage
Created by Guest
Created on May 7, 2026

Configurable attachment/version retention policy

Current DataStage/CAMS import behavior creates a new attachment/version every time assets are imported using the “replace” option. In enterprise CI/CD environments with automated deployments and shared dependencies, this quickly reaches the current 100-version limit, causing deployment failures.

The is a workaround that requires manual execution of cleanup scripts (deleteAttachments.sh) to remove old attachments, which is not a sustainable long-term solution for automated enterprise deployments.

We request the following enhancements:

  • Make the CAMS attachment/version limit configurable by administrators.
  • Provide automatic retention and cleanup policies for old pipeline versions/attachments.
  • Improve “replace” behavior to avoid creating unnecessary versions when no actual asset changes exist.

These enhancements are required to support scalable and reliable automated deployments without introducing operational risk or manual maintenance tasks.

Needed By Yesterday (Let's go already!)