Updating large database objects
Use this procedure to update large database objects or LOBs for Landmark business objects. This procedure applies to persistent fields of type Text, BinaryObject, and BinaryDocument, such as resume or image files, and provides a means to load the LOBs into the database quickly than using a Landmark application to load them one by one.
These are the main steps to update LOBs:
- Use the action in order to create a template of a CSV file for a single business class. This CSV file contains the LOB fields with no values. You populate this CSV file with references to file locations relative to the FTP directory. Any path delimiters must be forward slashes /. If a file reference is not provided, no database change is made for that field. To delete an LOB, you can specify a reference to a zero-length file.
When you use the action, you need to specify the fields needed to locate the specific row to be updated with file references. The CSV input file must include all fields of at least one index set that does not allow duplicates. These fields are not updated and use only to identify the records. You can add more non-LOBs fields to aid in identifying the records to update. Only LOB fields are updated.
- Use the action and the option in order to check if it can both locate the record in which to load the LOBs and locate the binary files based on the file references.
- Use the action in order to load the LOBs into the database. A LOB's associated MimeType and DocumentTitle type fields are implicitly updated if they exist just as they would if you were to import the LOB through the application. Any errors are written to an error zip file that contains CSV files with the problem records.
- The input files are required to be in CSV format.
- The input files must have headers.
- Input files must include the file references for the LOBs and all the fields of a unique index that does allow duplicates.
The path of each file reference must start with the expression, %ROOTPATH%/. This expression refers to the root path on your FTP server where the Landmark Administration Console obtains the item.
- Any path delimiters must be forward slashes /.