Skip to Main Content
Integration


This is an IBM Automation portal for Integration products. 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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


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.


Status Not under consideration
Workspace App Connect
Created by Guest
Created on Nov 17, 2024

Make ID mapping optional

When defining the model, it requires me to have a mandatory ID. In doing so, it is mandatory for me to specify the ID. However, in a RDBMS, we do not usually specify the ID when to insert a row. We allow the database to generate an ID. This is not ideal. Recommend to make ID mapping optional.

Idea priority Low
  • Admin
    Ben Thompson
    Reply
    |
    Dec 2, 2024

    Thank you for taking the time to raise this enhancement request but unfortunately currently there is insufficient detail here for us to be able to judge the merit of the suggestion. Which kind of "model" and which kind of "ID" are under consideration here … Is this perhaps discussing a Designer REST API interface where it is mandatory to have an ID field in the model? Or given the comment about databases/RDBMS is this something to do with using a Graphical Mapping node to map fields to a database table structure. Or perhaps this is about something else entirely. Status updated to Not Under Consideration … but please feel free to raise a new idea with more detail and we would be happy to consider.