McDewey

Correcting Errors Using Failed Objects File When you run BAT, it copies each record that it cannot process to a failed objects report file, along with the reason that the record was not processed correctly. For example, in the following CSV file, the first record includes an invalid entry for the Country field, and the second record specifies a template that is not a voicemail user template: Alias, City, PostalCode, State, Country, TemplateAlias Jsmith, Beverly Hills, 90210, Ca., United States, VoiceMailUserTemplate BRobertson, Seattle, 98121, WA, US, AdminUserTemplate Using this file to create users with voice mailboxes produces the following failed objects file: FailureReason, alias, city, postalcode, state, country, templatealias United States is invalid for column Country|, Jsmith, Beverly Hills, 90210, Ca., United States, VoiceMailUserTemplate Object not found or is not a template: Parameter = [@TemplateObjectId], Table = [vw_SubscriberTemplate], Column = [Alias,ObjectId]|, BRobertson, Seattle, 98121, WA, US, AdminUserTemplate The FailureReason column, which provides information about the invalid data, is added before the first column. To correct errors, do the following procedure to edit the failed objects file, rename it, and use it as the input file when you re-run BAT. Note that depending on the type of problem with the data in the CSV file, for each problem record, BAT may report multiple errors or only the first error encountered. Therefore, after you correct errors, BAT may detect additional errors in the same record when the data is processed again. Thus, you may need to repeat the correction process, which is running the tool and correcting an error, several times to find and correct all errors. Correcting Errors Using the Failed Objects File Procedure Step 1 If the Bulk Administration Tool operation results in any failures, you can immediately inspect the failed objects report file by selecting Download the Failed Objects File. Step 2 Open the file and correct all problems with the data, as indicated by the information in the FailureReason column for each record. Step 3 Remove the FailureReason column or change the heading to “junk.” Step 4 Save the file as a CSV file with a new name after editing the data. Step 5 Run BAT again with the CSV file that you saved in Step 4 as the input file. Note Each time that you run BAT, the failed objects file is overwritten (unless you specify a new name for the file each time you run the tool). Step 6 Repeat this procedure until all records are processed without error. Note If you have navigated away from the Bulk Administration Tool page, you can go back and select the Display Last Operation button to bring up a download link for the output file from the previous operation. If you need a failed objects file from more than one previous operation, you can use the Command Line Interface (CLI) command “file view activelog System Administration Guide 267 Tools Correcting Errors Using Failed Objects File