Label | Explanation | Data Type |
Input Dataset
| Geodatabase table or feature class to add attachments to. Attachments are not added directly to this table, but rather to a related attachment table that maintains linkage to the input dataset. The input dataset must be stored in a version 10.0 or later geodatabase, and the table must have attachments enabled. | Table View |
Input Join Field
| Field from the Input Dataset that has values that match the values in the Match Join Field. Records that have join field values that match between the Input Dataset and the Match Table will have attachments added. This field can be an Object ID field or any other identifying attribute. | Field |
Match Table
| Table that identifies which input records will have attachments added and the paths to those attachments. | Table View |
Match Join Field
| Field from the match table that indicates which records in the Input Dataset will have specified attachments added. This field can have values that match Input Dataset Object IDs or some other identifying attribute. | Field |
Match Path Field
| Field from the match table that contains paths to the attachments to add to Input Dataset records. | Field |
Working Folder
(Optional) | Folder or workspace where attachment files are centralized. By specifying a working folder, the paths in the Match Path Field can be the short names of files relative to the working folder. For example, if loading attachments with paths like C:\MyPictures\image1.jpg, C:\MyPictures\image2.jpg, set the Working Folder to C:\MyPictures, then paths in the Match Path Field can be the short names such as image1.jpg and image2.jpg, instead of the longer full paths. | Folder |
Derived Output
Label | Explanation | Data Type |
Updated Input Dataset | The updated input dataset. | Table View |