Hi All, Not sure if this is the correct forum, but has anyone had a warning like this when inserting their RISE module into their LMS (our's is Oracle Taleo). Any suggestions?
Warnings
· LoadMetadata (Manifest): LoadTechnical: Unsupported childNode found in Technical Metadata: pkgprop:ScormEnginePackageProperties
I haven't seen that error message before - what LMS option did you choose to export with?
I'd also suggest testing it at SCORM Cloud, that should help determine if the error is specific to LMS. If it doesn't happen at SCORM Cloud, I'd suggest reaching out to your LMS admin.
It looks like your email signature came through when you replied via email. You can remove that if needed by clicking ‘Edit’ beneath your response. Here’s a quick Peek video if you need help.
6 Replies
Hi Darlene,
I haven't seen that error message before - what LMS option did you choose to export with?
I'd also suggest testing it at SCORM Cloud, that should help determine if the error is specific to LMS. If it doesn't happen at SCORM Cloud, I'd suggest reaching out to your LMS admin.
Hi Ashley, Sorry for the delay getting back - it was SCORm1.2
No worries Darlene, were you also able to test at SCORM Cloud?
Do you know if Oracle requires SCORM 1.2, or could you try with SCORM 2004 option?
Yep tested to SCORM cloud, and it works fine. It's obviously an LMS thing - Ill check with ORACLE.
Thanks for the update Darlene :)
It looks like your email signature came through when you replied via email. You can remove that if needed by clicking ‘Edit’ beneath your response. Here’s a quick Peek video if you need help.
Hi I received the same warnings message on my scorm 1.2. I tested them on Scorm Cloud which reports:
Parser Warnings
Congratulations, your manifest looks great!
My Scorm packages get uploaded ok and work fine in most LMS, but in some they get uploaded with Warnings, like in Darlene's case:
· LoadMetadata (Manifest): LoadTechnical: Unsupported childNode found in Technical Metadata: pkgprop:ScormEnginePackageProperties
Any idea?
Thanks!
ET
This discussion is closed. You can start a new discussion or contact Articulate Support.