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 Submitted
Workspace Cloud Pak for Data
Created by Guest
Created on Mar 25, 2026

Differentiate API Success Responses When No File Is Uploaded (Volume API / upFile Handling)

Problem Statement

When calling the CP4D Volume API to upload a file, the endpoint returns the same generic “Success” response in two different cases:

  1. A file is actually uploaded, and
  2. No file is uploaded (e.g., due to a missing @ in curl or an automation error), in which case the API silently interprets the request as a directory‑creation operation.

This makes it impossible for automated workflows to reliably detect when a file upload has actually failed. From an end‑user and automation perspective, this behavior is misleading because the system confirms success even when the intended action did not occur.

Current Behavior

  • The upFile field in the API only accepts actual file payloads.
  • When no file is detected, the API performs mkdir -p and always returns a success message.
  • This behavior has existed for many years and is currently considered “working as designed.”

    more details with dev team https://github.ibm.com/PrivateCloud-analytics/Zen/issues/45789
Needed By Quarter