LiveLink Object importer is written with the SDK,so with SDK you can do anything.Now I am assuming the csv file that you are saying is an index of the actual files to be imported into livelink.Using VBA programming on excel you can create a loader script file which the object importer can then understand to upload into livelink.You did not mean you had a csv file,that you needed uploaded,then you shouldn't have to go thru this way.Livelink does not care what the file extension is it pretty much can handle csv.
For eg:assuming your csv file had
MyDocument,\\uncpath\somefolder\filename.txt,text/html
Now if the above are true here is a minimal syntax for the
importer.The syntax for documents,folder everything is vailable in the object importer documentation
Code:
<node type="document" action="create">
<location>Enterprise:Upstream</location>
<title>MyDocument</title>
<file provider="EXTSHARED">\\uncpath\somefolder\filename.txt</file>
<mime>text/html</mime>
</node>
Now when you run the object importer it parses the lines (xml looking) between node and </node> and puts it into the livelink folder where you want it to g

bject importer can be run manually and unattended.Most of where I have used ObjImporter is to bring in large amounts of data like in a data migration project.We have suppliers giving us dvd's containing data and I write up the xml looking script file and import the data.Bottom line is this,the script file should contain a)where in livelink the thing gets to go 2)Where can the livelink process find the actual file
Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937