ObjectImporter and long paths

Yosi Maurer

We are using ObjectImporter to import files from unc.
ObjectImporter is failing for all network paths larger then 260 charachters.

This is often a known limitation with old .net programs.

Is there a way to pass this limitation?

appuq

If you can successfully prove that the OI code will fail every time it exceeds that, some ways to workaround that would be

1. Write to OT support showing that this is the case and ask what can be done.
2. Switch to other methods like REST or SOAP.
3. Work at your end, for example.g you are generating the XML so in your code, you would try to work a logic if path > 260, copy the file to the alternate short location. Or even mount drives that hide them for livelink.So instead of \\long path, you would say D:\myfile

PS: The Object Exporter code has some handling so it can pass extremely long paths because livelink is a database app, so it can have very long paths, so when they download it, you can see OE code doing a normalization routine. The File dropin in Oscript is not accessible to us developers but I would look through its documentation to see if OT says it cant handle 255+ characters