The Batch Engine allows calling any QBO module and operation from Excel spreadsheet. Examples include:
To enable this flexibility, the Excel spreadsheet must include two key columns:
Most other columns in the spreadsheet row are stored in ImportFileQueue.ParameterXml, and will be passed as parameters to the operation being called.
For example, creating a Loan via the front-end involves calling Loan.ashx/Save?Loan=123456789&UPBAmount=550,232.17. An Excel spreadsheet being passed to the Batch Engine would include these columns:
The Batch Engine will:
Note the "most other columns" note above. The exception to this rule is columns matching the ImportFileQueue table's column will populate the ImportFileQueue columns, instead of the target ClassName. To work around such conflicts, you may specify ParameterString.
For example, assume you wish to send emails to borrowers, associating the email to a loan:
Both ImportFileQueue and Message have and Object and ObjectID column, so this will bind the ImportFileQueue to LoanID 12345, instead of binding the Message to LoanID 12345.
The workaround using ParameterString is:
Using the standard QBO Save method assumes that the columns in the spreadsheet match the column names of QBO tables. Spreadsheet provided by third parties may contain column names not recognized by QBO, or column names that must be mapped to QBO data in a customized manner. To accomplish this:
For example, assume that a title vendor named Acme Title provides a spreadsheet of data containing title, public record, message and other data related to a title order. You might: