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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Idea / RFE Review. Apologies for the length of time this RFE has been held in Uncommitted Candidate / Future Consideration status. As you may be aware, we have been pursuing a technical strategy for a few years now to simplify the ability of our integration portfolio when communicating with 3rd party SaaS based applications. This has largely involved new connectors for the Designer flow authoring tool, and in this tool we may in future expand to support some kind of Excel connector. Meanwhile, in the Toolkit flow programming model we are now unlikely to create a message domain / parser in support of Excel. As noted in previous comments, DFDL csv support and .NETInput nodes provide two alternative methods to get data from Excel into an ACE message flow and we feel these solutions provide good options for Toolkit flows.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - WebSphere
Product family - Integration
Product - IBM Integration Bus (WebSphere Message Broker) - IIB
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Connectivity and Integration
Product - IBM Integration Bus (WebSphere Message Broker) - IIB
Thanks for raising this requirement for an Excel parser, which we would like to implement in time. Today you can either export the spreadsheet data into a format that is easily parsed (e.g. a CSV file), or you could use a V9 .NETInput node to interact with the file directly using (for example) the C# APIs.
Thanks for raising this requirement for an Excel parser, which we would like to implement in time. Today you can either export the spreadsheet data into a format that is easily parsed (e.g. a CSV file), or you could use a V9 .NETInput node to interact with the file directly using (for example) the C# APIs.