![]() ![]() In this case, OrderHeader node occurs once while OrderItem node can occur any number of times. Specify the name and occurrence of each sub-node in Recordset Structure. See this link for exhaustive list of available parameters. If you do not want this extra node to be inserted, you can set the parameter ignoreRecordsetName to true (Thanks Mike for this input). If left blank, it defaults to ‘Recordset’. Recordset Name defines the root node under which rest of the XML will be created. Document Name and Namespace correspond to the message type from the Integration Repository. Specify File Content Conversion as message protocol. The figure below shows a typical configuration of the sender file adapter. Sender File Adapter Configuration with Content Conversion ![]() The adjoining figure shows such a file with minimal fields. Every field has different lengths and there are no field separators. The first row has header information like customer details and order details whereas the remaining rows have order items details. Assume that sales order is received in form of a text file. ![]() Let us take an example of a simple sales order. For example if it has different number of columns of information on different rows. In this article we will understand how to deal with File Adapter when file structure is a bit complex. ![]() We have discussed Simple File Adapter Configuration as well as File Content Conversion for a simple structure CSV file. ![]()
2 Comments
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |