Link to open shared folder

Hi all,

I'm fine inserting hyperlinks to open files & URLs but I'm struggling to get a link inserted to open a shared folder.

I need to open a shared folder '\\intranet\vids' which holds a number of files. The files need to be stored in the folder rather than in the Storyline package itself.

I've tried inserting a URL but it strips a \ from the start of the link and I can't seem to get it working with JavaScript.

Any advice greatly appreciated!


5 Replies
David Blanchard

Hi Ashley,

Thanks for the reply. I'm using update 6: 1407.2208

Unfortunately the fix you've linked to is almost the opposite of my problem. My issues is that Instead of adding extra slashes it's removing one. I'm not sure if I've explained myself correctly in my first post.

My project is saved locally and I have no problem publishing it.

My issue is that I need to have a link in a slide that opens a network folder (not a URL or a specific file) using its UNC (Universal Naming Convention) path so the folder opens in windows explorer and presents a list of files to the learner. The path is \\intranet\vids but when trying to enter this path as a 'Jump to URL/File' trigger it is saving as \intranet\vids, stripping out the first \ which renders the link unusable.

Is there a way to have a link in a slide that opens a network folder rather than a URL/File?


Ashley Terwilliger

Hi David,

Ah, thanks for the clarification. I now remember another thread with the same issue - and although I don't have a network folder as you mentioned to test it, it seems I was able to update the trigger as it was listed. It seems that didn't resolve that particular users issue - so you may also want to connect with her to see if she has anything else to offer. 

Also, are you able to place the folder on a web server so that you could link to that directly? 

Ashley Terwilliger

Hi Thu,

Is your problem also connected to linking to files within an Intranet set up and seeing the extra slash removed? I don't see any further update from David here, so I don't know if or how he was able to resolve it. You may want to look at messaging him directly using the "contact me" link on his profile to see if he's able to share an update. 

I do see that we shared a similar issue with our QA team, and that issue is still open for investigation. I'll include this thread in the report filed with our team so that we can update you here once there is additional information to share.