Don't quite see how ExecuteSQL can contribute to the solution here. Since FileMaker assumes that each row of the spreadsheet is a different record and each column is a field, You'll need to import this data into some kind of staging table with a script to loop through the imported records sending data about the shipment as a whole to records in the shipment table and line items data to the line items table.
Thank you for the response! I am going to do as you suggested and loop through the records with a script. I am fairly new to scripting and have been trying to figure out the best way to import all the reports that are generated by Amazon using a staging table.
Don't quite see how ExecuteSQL can contribute to the solution here.
I guess I don't fully understand the executeSQL script step. I found it easy to write a query to gather the information I needed from the reports but I'm guessing by your response there is no way to use the data from the query to create new records in a different table. Is that correct?
There's an Execute SQL script step used to send data to an ODBC data source.
There's an ExecuteSQL() function you might use inside a calculation, but it, as you describe, is only used with SELECT queries to "read" data from a FileMaker Table, not to create new records.