Skip to Main Content
IBM Data and AI Ideas Portal for Customers


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:

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

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is: https://hybridcloudunit-internal.ideas.aha.io


Status Future consideration
Workspace SPSS Modeler
Components SPSS Modeler
Created by Guest
Created on Apr 24, 2017

PARSE node

Virtually all the source (input) nodes have some way of parsing out data items from a record or row. However, there is one source that does not have this functionality, and that is an incoming arrow from within the stream itself.

Of course, this functionality can be achieved with several hundred Derive nodes - but that makes the stream huge, unwieldy, and error-prone. A Parse node is a much more elegant solution. Increasing numbers of users are finding Modeler unwieldy; this would help.

The logic for the parse node already exists; it is in the Fixed-Width node. In fact, a user could accomplish the same functionality as a Parse node by simply writing out records with a Flat File export node, and then reading from the same file with a Fixed-Width source node, and parsing out the records into fields. So, why are we required to incur the overhead of a file IO, with its tremendous slow-down, to accomplish this?