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 Cloud Pak for Data
Components DataStage
Created by Guest
Created on Apr 27, 2026

Execution Order of Before SQL and SELECT with Runtime Column Propagation Enabled in Redshift connector.

When Runtime Column Propagation (RCP) is enabled in Redshift connector, DataStage executes the SELECT statement during the stage check phase to infer metadata. If the SELECT depends on a table or view created dynamically in Before SQL, the job fails because the object does not yet exist.

When RCP is disabled and schema is explicitly defined in Redshift connector, the execution order works correctly:

  1. Before SQL executes first and creates the required object.
  2. SELECT statement executes next.
  3. Job completes successfully.

Enhancement Request:
Allow Before SQL to execute prior to the SELECT statement even when RCP is enabled, so that required tables/views can be created first. Afterward, allow RCP to infer metadata. This functionality is critical for jobs that rely on dynamically created objects and use RCP.

Needed By Not sure -- Just thought it was cool