This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
I think I've come up with a viable solution, but it's a bit of a hack.
What you'll need to do is leverage the Run Command tool to write out something like the following:
cd "C:\Users\home\Desktop\parent folder\longfoldername" & dir > "C:\Users\home\Desktop\parent folder\dir.txt
This will create a file named dir.txt listing the contents of the directory in the parent folder of the long folder. You can then read this in via an Input tool and parse it in the usual way.
The dir.txt file will look something like this (looks short as in this case I only had one dummy file in there):
Volume in drive C has no label.
Volume Serial Number is 4E24-CEDF
Directory of C:\Users\home\Desktop\untitled folder\thisisalongfoldernamethisisalongfoldernamethisisalongfoldernamethisisalongfoldernamethisisalongfoldernamethisisalongfoldername
05/15/2019 04:11 PM <DIR> .
05/15/2019 04:11 PM <DIR> ..
05/15/2019 04:10 PM 0 file.txt
1 File(s) 0 bytes
2 Dir(s) 243,379,408,896 bytes free
Even after changing the registry to enable long windows file names, I'm still having some trouble in Windows with long file names so I suspect that something else might be giving me trouble. The solution proposed by @jamielaird should work, although I just gave up on this as it was related to a time sensitive analysis and I could move things to folders with shorter paths for now.