Files containing Ids of records to include/exclude can be loaded into the application by using one of the following methods:

Load Filters From File

File Names

Each file's file name must match the object's API name (the API name is that same as the label with the spaces converted to underscores ("_") and suffixed with "__c") and have the extention ".csv" (csv stands for comma-seperated values). For example, if a file contained the Ids you want to include for Accounts (Standard Object), the file name must be "Account.csv". If the file contained the Ids you want to include for MyCustomObject (Custom Object), the file name must be "MyCustomObject__c.csv".

Header Row

The CSV file can have a header row defining the column labels, although this is not required. The application automatically detects if a header row is present by testing the first 15 characters in the first line to see if it contains anything which is not a letter or digit, and since the column name (Id) in "Id,ColA,ColB,etc" is within the first 15 characters, it would see the comma after "Id" and figure out that the first row is a header row and ignore it.

The every row in the CSV file must have the Id as the first column in the file. The remaining columns are always ignored (this makes it easy to identify records you want to include by exporting them using other utilities such as Apex Data Loader or saving Reports from Salesforce in CSV format. Remember, the application only reads the first 15 characters (the Id) of every row, the remaining characters are not used by the application in any way.

The file can contain blank rows and these blank rows will be ignored.

Verification

After reading each file, the application will verify the Ids against Salesforce and use only the valid Ids it finds in Salesforce.