I recently made the switch to Storyline 360. I previously had Storyline 2 and was able to publish for the web, create the .aspx file, and upload to SharePoint through Explorer. In Storyline 360 I can not get the same results with that process. Instead, upon clicking the .aspx file on SharePoint, I receive a prompt to save the .html file. If I click save, a blank window opens. I have tried this in both Chrome and Internet Explorer 11. Is there something I have to do differently when using 360?

Hi friends, I feel that it would be supremely helpful to the entire Storyline community if Articulate provided support for SharePoint, OneDrive, and now Teams. They are viable and extremely ubiquitous intranet and extranet collaboration platforms and seem like a perfect way to deliver learning and performance support content. I've tried the numerous hacks that are documented in this discussion thread and some work, but do so inconsistently. Is there nothing that the folks in development can do to help out the user community on this topic? Do we really need to hack all these various systems or the content we've developed to get this to work? In many cases, we're working with a consulting client and have little or no influence in the client's intranet platform. But, Office 365 and it's family of products are so widely used, that it seems a disservice to the community and our clients or employers to produce content that can't be shared on that platform. Yes, learning management systems are the most appropriate platform to provide content to learners, when tracking progress and completion of training modules or courses is important. However, there are many use cases where SharePoint is a more appropriate platform because it's integrated with a team collaboration site and is a performance support tool or just information distribution. Question for Articulate staff: is there anything being done on this? Or should everyone on this thread just give up and stop trying to make this work? I know I've spent countless hours trying to get this to work. I'm not trying to be sarcastic, honestly. If the answer is 'no', then the answer is 'no'.

Hi Lisa, Well, looks like you're doing everything correctly and you still get the Save As... prompt. What that tells me is that the SharePoint server is set to not allow uploaded .ASPX files to run and prompts the save as. This may require you to contact the admin of the SharePoint environment (or the document library you're using) to enable running of ASPX files. You could also request that HTML files be enabled as well. If you can get that administrative change on the server side, you wouldn't need to do any of the copying and renaming. However... I've found getting those kinds of changes done at the infrastructure level is a tall order and affects security policies that most orgs have in place. So... this is the reason for the copy/rename workaround. Since you're working in SharePoint, you probably have Office 365, which includes OneDrive. OneDrive is often more "open" to external content and may be set to allow ASPX and even HTML, sometimes. Again, this is controlled by organizational security, etc. I'd recommend seeing if you can upload your content to OneDrive and test the running of ASPX (and HTML, while you're at it!). Every environment is a little different (duh, John!) and it often takes some cajoling to get IT or SharePoint admins to adjust things for SL content to run. Having worked in IT and also on the Learning & Development side of things, you may be able to get this adjustment to security made without too much trouble. On the other hand, network and data security seems to get more locked down as time goes by, rather that getting looser. My experience is that spending time on the workaround may be more fruitful that spending time trying to adjust an org's security policies. Let me know if the OneDrive approach is possible and if it worked for you! I'm also curious if Articulate is looking at SharePoint integration with Storyline. With such a ubiquitous corporate intranet/extranet platform like SharePoint, it seems like a natural place to distribution web-based training outside the LMS environment. Thanks! John

Hi SharePoint Explorers! Well, it seems like something has changed recently in SharePoint that is preventing anything I publish from running. I've tried the HTML > ASPX renaming approach I've discussed here previously, but that no longer works. I am at my wit's end on this. The only thing I've been able to do is load a published project folder onto OneDrive and then link to that from SharePoint. At this point, OneDrive (or on a web server other than SharePoint) seems to be the best approach. It seems like there are a growing number of users who want to publish to SharePoint from SL and SL360. If enough of us add this integration to a feature request, it could happen. Thanks to Articulate Support for listening to this awesome community!!! I'm sharing a mock-up of the SL 360 Publish dialog with a SharePoint option to inspire everyone! ;-) https://articulate.com/support/contact/feature-request

Hi Leslie, I learned that this process still works if I use the story_html5.html file to create the .aspx file. In the past, I always used the story.html file. Thank you!

Also having issues with running Storyline 360 content on SharePoint. A while back I tried renaming story.html to story.aspx. The file runs on SharePoint, but because the code in story.html checks browser type and availability of Flash, it eventually redirects to story_flash.html or story_html5.html. At that point, SharePoint wants to download one of those HTML files. I renamed those two files to have an ASPX extension, and then opened story.html in Notepad and easily found the references to story_flash.html and story_html5.html, changing those to look for the renamed ASPX files... And it works! Not too much work to get things running on SharePoint. However... I then ran into issues with imported content from Engage. Like Storyline, Engage publishes a handful of HTML files, which SharePoint insists on downloading. So, I found all those files (a bunch, because I love the rapid development I can do with Engage interactions!!!) and renamed them to have an ASPX extension. And, without getting into the gritty details, I had to use Notepad to go into the code and changes references to the HTML files over to ASPX. No luck this time. It appears that published Engage interactions seem to use JavaScript, CSS, and XML to generate the URL used in the slide frame in Storyline for the interaction. (okay, I got gritty there for a second) The bottom line is, the Storyline content runs just fine (with either Falsh or HTML5) but the interactions result in a 404 page not found error. I haven't tried, but I suspect the same might be the case for content developed in QuizMaker and imported into Storyline. Yes, I could recreate my interactions in Storyline, but I like Engage. I asked the SharePoint admin to see if they could just make an adjustment on the server to allow the running of HTML files, rather than forcing a download (Save/Save As) but IT security won't allow that to happen. Anyone experiencing this issue? Any clues? Seems like this could be a feature request to allow choosing HTML or ASPX as the output "wrapper" format... or even a SharePoint tab on the Publish page options. ;-) Thanks, John

Storyline 360 to SharePoint | Articulate

71 Replies

LeslieMcKerchie
Staff
7 years ago
So glad to see that this conversation is still helping out within the community.

Thanks for chiming in to share Sharmaine and welcome to E-Learning Heroes :)
ITADLD
Community Member
7 years ago
Hi folks,

Just wanted to chime in that not only do you have to change all .html to .aspx, but also within those .html files, you need to run a find and replace for .html to .aspx. Then it will run fine. Just wondering how I can save scores onto a Sharepoint list, the next issue to conquer!
AlistairDootson
Community Member
7 years ago
I have a similar problem, running on Sharepoint online.

The html files do not try to download - the story.html opens blank, story_html5.html opens and spins forever.

If I rename to aspx, then they get downloaded and open in editing mode, so that older workaround really doesn't work.

I've tried most of these fixes and I'm getting nowhere, I have tried locally and it runs fine!

Help most appreciated!

Ali
JohnLuttrell-43
Community Member
7 years ago
Hi SharePoint Explorers!

Well, it seems like something has changed recently in SharePoint that is preventing anything I publish from running. I've tried the HTML > ASPX renaming approach I've discussed here previously, but that no longer works. I am at my wit's end on this. The only thing I've been able to do is load a published project folder onto OneDrive and then link to that from SharePoint.

At this point, OneDrive (or on a web server other than SharePoint) seems to be the best approach.

It seems like there are a growing number of users who want to publish to SharePoint from SL and SL360. If enough of us add this integration to a feature request, it could happen. Thanks to Articulate Support for listening to this awesome community!!!

I'm sharing a mock-up of the SL 360 Publish dialog with a SharePoint option to inspire everyone! ;-)

https://articulate.com/support/contact/feature-request
- RoniBorri
  Community Member
  7 years ago
  
  John Luttrell
  
  Hi SharePoint Explorers!
  
  Well, it seems like something has changed recently in SharePoint that is preventing anything I publish from running. I've tried the HTML > ASPX renaming approach I've discussed here previously, but that no longer works. I am at my wit's end on this. The only thing I've been able to do is load a published project folder onto OneDrive and then link to that from SharePoint.
  
  At this point, OneDrive (or on a web server other than SharePoint) seems to be the best approach.
  
  It seems like there are a growing number of users who want to publish to SharePoint from SL and SL360. If enough of us add this integration to a feature request, it could happen. Thanks to Articulate Support for listening to this awesome community!!!
  
  I'm sharing a mock-up of the SL 360 Publish dialog with a SharePoint option to inspire everyone! ;-)
  
  https://articulate.com/support/contact/feature-request
  
  Hi John,
  
  I have seconded your feature request :)
  
  In the meantime, can you explain how you got it to work through OneDrive? I've uploaded the published web content to OneDrive, but not sure if I should still be changing file extensions, or what to have Sharepoint link to.
  
  I've built a fab little interaction in SL360 but I'm lost on how to get people to see it outside of our LMS. I'm feeling a bit inept!
  
  Thank you!
  - KirenJagdev
    Community Member
    7 years ago
    Hi Roni,
    
    After looking through the threads I found that in OneDrive if you open your html5 file in notepad or the equivalent on a MAC and then resave it as .aspx it seems to work :)
AshleyT-Pollard
Staff
7 years ago
Hi John,

I love your enthusiasm for this feature and sharing some details here. Thanks for sending along to our team as an official feature request too. Although we don't currently have publishing options that refer to specific hosting solutions, it's always good to know that it would help you and others!

We'll keep folks posted if something like this is added to the roadmap.
- JohnLuttrell-43
  Community Member
  7 years ago
  Thanks so much, Ashley! Storyline just keeps getting better and better! :-)
- AldinaGoncal236
  Community Member
  6 years ago
  Any news about this item? it is definitely still a need. I am currently desperately looking for a solution as our intranet is in SPO and we can't share our content with our audience as we would want to.
  
  Any guidance would be really appreciated!
  
  Aldina
  - LaurenDuvall
    Staff
    6 years ago
    Hi Aldina!
    
    Great question!
    
    This is specific to SharePoint, and the way content is uploaded to SharePoint. It sounds like other community members are uploading Storyline 360 courses to SharePoint in this discussion.
    
    I'd also recommend checking with SharePoint to see if they have tips to share when uploading content in html format.
CynthiaPare
Community Member
6 years ago
Hi everyone!

I'm looking for a solution to get a Storyline 360 publication (html5) to work on Sharepoint Online. Did anyone end up finding a solution as of now? I can't seem to find any recent post regarding this.

Thanks in advance for the help!
- MalcolmMcKin191
  Community Member
  6 years ago
  Hi Cynthia,
  
  I'm not sure if this will suit your situation, but it seems that the best option is to upload your files in to OneDrive (replacing .html with .aspx as described in other posts in this thread).
  
  This solution works for me, although - somewhat ironically - it doesn't work in Microsoft Edge browser. I recommend learners use Google Chrome or IE.
  - CynthiaPare
    Community Member
    6 years ago
    Hi Malcom,
    
    Thank you for jumping in, but I really have to find a solution using SharePoint. It's for a client, so OneDrive isn't an option for them.
    
    Thanks anyway!
JohnLuttrell-43
Community Member
6 years ago
In related news, I ran across a similar issue with Adobe Captivate. I think this could be a general issue with SharePoint and content from both Storyline and Captivate. It looks like there's an issue on SharePoint with .json files. JavaScript Object Notation (.json) files are used for application-server data exchange. But, .json files are blocked by default on SharePoint servers.

Here's an article about publishing Captivate to SharePoint and there's a note at the top about using the admin tool on the SharePoint server to allow .json files to be used:

https://helpx.adobe.com/captivate/kb/upload-captivate-published-output-sharepoint.html

I don't have that level of access for any SharePoint server, but I think it could be a clue to getting Storyline content to run on both SharePoint and OneDrive with the .html > .aspx approach.

Anyone out there have full Admin rights on a SharePoint server? ;-)
LeslieMcKerchie
Staff
6 years ago
Hi Cynthia,

Just want to pop in about the file type you noticed/mentioned here.

We simplified the published output in Storyline 360 builds 3.35.20995.0 and later. When you publish HTML5-only or Flash-only courses, Storyline no longer generates these files in your published output:

• index_lms_flash.html
• index_lms_html5.html
• story_flash.html
• story_html5.html

You'll only see the files above when you publish courses with both HTML5 and Flash formats.

We recommend pointing to story.html or index_lms.html depending on the publish.
LizPisarczyk
Community Member
6 years ago
Hello Everyone,

I found this thread super helpful, however, since this conversation is from 2 years ago, I am wondering if these fixes no longer work. I am trying to upload a Storyline 360 story to Sharepoint by following all the instructions here. Unfortunately, my aspx file is prompted to download every time. Articulate is no longer recommending that users download the Classic story view - meaning the new Modern view does not include the Flash html paths that have been mentioned.

Does anyone have an update to this conversation with the newer options in Storyline?

Thank you in advance!
AldinaGoncal236
Community Member
6 years ago
Thanks Lauren,

That link takes me to a conversation with around 9 years now.. not sure if it's helpful, thanks for answering. Other links to mention that this item would/could be included on the roadmap so hoping that was any developments on that.

Thanks

Aldina

Forum Discussion

Storyline 360 to SharePoint

71 Replies

Related Content

Getting Started with Storyline 360

Storyline 360: Applying Merge Shapes

Storyline 360: Create Content with AI Assistant

Storyline 360: Corner Radius Formatting

Creating Performance Meters in Storyline 360

Learn

Connect

Discover

Community

Company

Trust Center