In addition to the info @engin_arlak shared, might I share that past experience with programmatically dealing with Excel files is something to avoid if at all possible. We used POI long ago. It was okay. But any change in the Excel, particularly if the Excel file is typically edited by people, can cause the process to fail. That’s true with any file format but with Excel it is exceedingly easy to inadvertently break things.
Reporting tools and BI components love spitting out Excel. Because they work well for humans. As a “bucket” for data transfer automation, they are less compelling. ![:slight_smile: :slight_smile:](https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/slight_smile.png)
Edit: anything that can create an Excel can generally create a delimited flat file too. Ask them to do that instead. And have them follow the typical conventions so that there is no data loss and delimiters can appear within the data without being treated as delimiters.
#Managed-File-Transfer#Service-Designer#Integration-Server-and-ESB#Flow-and-Java-services#B2B-Integration#webMethods-io-B2B#webMethods-cloud#webMethods-io-Integration#Adapters-and-E-Standards#webMethods