Skip to Main Content

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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace App Connect
Created by Guest
Created on Nov 9, 2015

Permit DFDL Editor to automatically create field names based on a sample file - eg CSV #EMEA #uki

We're talking Build time, within the IIB Toolkit's DFDL Editor.

At the moment, when one starts to build a new Message Model (schema) for CSV data, the wizard lets one define the EndOfRecord character(s) and the number of fields, as well as whether the first record/row is a Header or not. It then creates a schema in which it assigns the *NAMES* of the elements as fieldnnnn (field1, field2 ... field10, field11... field100, field101 ... etc).

This is all very well and works. But the names fieldnnnn are not very friendly. It means that when using the Mapping node, it is difficult and cumbersome to work out which elements one should be mapping to/from. This is particularly the case for customers with very wide CSV files (by which I mean 100 columns or more).

In nearly all cases that I have come across, these customers' CSV files *DO* use record/row 1 as a Header, and in that Header are the names of all the fields/columns. So the customer has quite reasonably asked "if these field names already exist in an example CSV file, can the DFDL editor analyse that example CSV file and create nicer field names ?".

So, technically, the requirement is for the DFDL editor to be able to analyse an example data file at Buildtime, and to extract data from that example data file when creating the schema. In this particular case, I want the DFDL editor to extract the column/field names from the first row/record of a CSV file, and then make a stab at creating element names based thereon.

Idea priority High
RFE ID 79488
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Admin
    Ben Thompson
    Feb 2, 2022

    RFE Review. Apologies for the length of time this RFE has been in the status of Future Consideration. Despite the provision of the pattern workaround supplied in the previous update comment, we still acknowledge that this feature suggestion would bring value to the product. The existing message model wizard could be furnished with a new page which lets you navigate to an example csv file which includes your desired fields (eg in a header row). We will continue to monitor for popularity. Status is maintained as Future Consideration.

  • Guest
    Jul 14, 2016

    Thanks for raising this RFE which would make an excellent enhancement to the DFDL editor. Meanwhile, I'm attaching a very simple pattern which we discussed when you raised this RFE which might help others in the interim until such time as this RFE can be delivered. I'm attaching several files to the RFE. Copying the example header file "Example.csv" into C:\File directory, and choosing default pattern values, results in the attached ExampleMessage.xsd (note that field1 - field5 have been replaced respectively with "mary had a little lamb").

    Status of the RFE is updated to Uncommitted Candidate.