Use FileLoad.  How to do so is explained in the Import/Export Guide, with FileLoad being chapter 13 in the 9350 document.
 It isn’t too hard, so long as you understand how to build the index files and what the differences are between the Web client version and the Java client version. If you have the files located on your PC, the Java client would be the one to use. If you can get them to the web proxy server, the Web client would be preferred.
 So far as I know, Import cannot be used to process attachments unless you are using a PDX or aXML source file. A PX can do it, but FileLoad is already there (but does require the necessary roles/privileges to even be able to access it).
 The basic question is, how many files do you need to process, and how often. If the count is over 50, I would recommend you use FileLoad. You will otherwise need to balance what needs to be done to use FileLoad versus what needs to be done to use a PX.
EDIT : And I forgot to tell you what to do if the count is < 50.   In that case, you can probably do it manually faster than you can train yourself to use FileLoad and get the index files together. Not that using FileLoad is hard in any way, but it does take practice and attention to detail to get correct. Always test using a small file (3-5 records) when doing a new attachment load, just to make sure you have the index format correct, and to make sure everything is running correctly. Also note that FileLoad does not care if the attachment is already there, it WILL attach the files that you tell it to.

Kevin’s information is very good. You need to build the index files but when you successfully complete the fileload do not hit Ok, but hit Cancel. I haven’t used this in a while but if you hit Ok, it loads all the files again and you need to manually remove them. This isn’t a robust interface but it does the job.

MD

Hi Steven,

You can look up to this thread –> https://myagileplm.com/questions/reg-agile-automation/
I have shared step by step details of bulk attachment upload using File-Load utility.

Regards,
Arif

Thank you Kevin, Michael, and Arif.  All useful info.  I followed the tips in the thread, Arif, but had limited success.  First, it was stated that if the files are on the local PC, that the Java client was preferred. Does that mean, with the right permissions granted, that the Web client still CANNOT access files on the PC.  I ask because I tried first to upload two file to two separate objects (one to a CHANGE and one to an ITEM), and the error log states that files could not be found.  When I tried the same index and files via the Java client, it worked… sort of.  By that I mean it attached to the CHANGE, but NOT to the ITEM.  That said, it also did not report any errors in that case, so I’m not sure what went wrong there.
I am also looking to make a utility that is relatively easy for end-users to use. Trusting them to even make the index file correctly, without a PX to do it for them, is a bit of a stretch.  Still, it is good to know this functionality exists.

Hi Steve,

Would you share your index file content? You can change the actual content, just looking for how you did the index file and in what order.
I did find the Java Client to perform this task better and we loaded parts onto a shared location that the server was linked to directly.

MD

Sure Michael.  Thanks for taking the time to review it.  The content of the index file for my case looked like this:

CHANGE,CO-0147324,,C:/CADTEMP/FILELIST.CSV,FILE,,
ITEM,2187010100U004,,C:/CADTEMP/2194610100000.pdf,FILE,,

Steve

Michael, I did figure out that I must specify the revision when attaching to an ITEM.  So if I change this…

ITEM,2187010100U004,,C:/CADTEMP/2194610100000.pdf,FILE,,

to this…

ITEM,2187010100U004,02,C:/CADTEMP/2194610100000.pdf,FILE,,

This is a little strange, because the instructions seem to indicate that the Rev is optional, which would imply that it might attach to the latest rev by default.  At least a fould a method that works though.