Aggregate Storyline project connecting multiple modules

We are creating an aggregate Storyline360 project. The initial file acts as a menu splash page to other Storyline created modules. We were able to create functional links to the other modules. We were able to publish locally without an issue. When we publish them to the LMS, we get an XML error message, "This XML file does not appear to have any style information associated with it".

Storyline seems to create a full asset inventory within the manifest—calling out every file in the build. Our issue with the XML error on the LMS is likely caused by not having the assets from all the modules included in the manifest. To manually add the directory paths to the core manifest will be labor intensive, with a high risk of path errors. Any suggestions on a practical solution?

3 Replies
Emerson Collins

Hi Alyssa,

Thank you for your response. Yes, we have tried the Web Object route. I'm not sure Storyline is generating the correct path when publishing the modules. Which makes sense, since Storyline will not aggregate multiple Storyline modules. Our LMS system doesn't open the web object.