Link to open shared folder

Hi David,

What update of Storyline are you using? We're currently on update 6 and there was a previous fix for that issue mentioned here.   As a reminder though, you'll want to work with local project files and link to local files as detailed here. 

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?

Thanks,
David.

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? 

Hi Ashley

Now, I have a problem like David, 

Might you respond that problems have any way to solved yet?

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. 

Was there ever a resolution on this? I need to link to a folder on a shared drive and not to a specific file. I get an error message.

Hello Randy!

Since this is a dated thread, we'll need to start troubleshooting from the beginning. Which version of Storyline are you using? We are currently on Storyline 360 (Build 3.46.23620.0).

Also, have you tried adding this folder or files to the Resources tab in the Player?

Lastly, would you mind sharing a screenshot of the error message you're seeing? If you're comfortable sharing the .story file with us, you can use this secure upload link, and we'll notify you when we receive the file!

I am having the same problem.  I have tried multiple times to link to a folder from a trigger and/or the Resources tab as shown on your above “Resources Tab in a Player.
This is the full file name

C:\Users\grider\Desktop\Operational Training\Residential Service and Transformer sizing\Curriculum\2021\Mod 3 R7\SC1\Enable Now

Attached is the StoryLine file (Module 3 SC1_Exe.story) and document with screen shots of the error messages.

Thanks for any advice!

Hello Guy! 

I appreciate you sharing the issue that you're currently experiencing. Please be sure you are viewing the published content in the environment it was published for and not on your local machine.

My first thought for your error is the file path length, which is already 127 characters. When published, this will expand:

Be sure the file paths to your projects and published output are well under the 260-character limit imposed by Microsoft Windows. (The publishing process adds characters to the file path you selected. If it exceeds 260 characters, your published output will be incomplete.)

Could you move your file to your desktop, reattach it to your resources, and see if this alleviates the error you're seeing? 

the exact problem exists. the file path to the folder was shortened to C:\Users\grider\Desktop\Mod 3 Scenarios.