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



Add a new idea Subscribe
Status Submitted
Workspace Cloud Pak for Data
Components DataStage
Created by Guest
Created on Oct 7, 2026

RELATED IDEAS

Sequential File Stage Should Support Header-Based Column Mapping When Using Schema Files

When using a Sequential File stage with a schema file, DataStage maps columns by position instead of by column name, even when "First line is column names" is enabled and the file contains a header row.

This behavior is inconsistent with the scenario where column definitions are maintained directly in the stage. In that case, DataStage correctly maps columns based on the header names, regardless of the column order in the source file.

In our environment, a change in the export tool caused only the column order to change. This led to job failures or incorrect data mappings, although the column names remained unchanged.

Current workaround: We would need to create and maintain dozens of separate flows or move the logic to Python/Jupyter notebooks to dynamically match columns by name.

Proposed solution: When a schema file is used and a header row is present, DataStage should provide the same header-based column mapping behavior that already exists when columns are defined directly in the stage.

Benefits:

  • Consistent behavior across both metadata definition methods.

  • More robust against source file changes.

  • Reduced risk of incorrect data mappings.

  • Less maintenance effort for generic ingestion frameworks.

  • Avoids the need to implement custom Python solutions for functionality that should be available within DataStage itself.

Needed By Yesterday (Let's go already!)

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.