I am publishing an updated Storyline file, and moving to our CRM to go into Canvas. When I publish to Web, all files (html5, mobile, story_content, meta, and story) update to the correct date, but the analytics-frame file doesn't update to the correct date, and I believe it is stopping the file from updating to the changes.
What is the date of your analytics-frame.html file? I have the latest version of Storyline 360 installed and the date of the analytics file is 10/29/2021 even when publishing a file today (11/12/2021). The analytics file in the published folder is the same date as where it originates from: C:\Program Files (x86)\Articulate\360\Storyline\player\{classic or unified depending on the player chosen}
If you have Storyline up to date but the analytics file is much older, that does seem odd. If not, I'm wondering if there's something else going on with your project.
I think you're all set then as far as the analytics file goes. As I noted, the analytics file is pulled from the Storyline 360 installation folder. Even though you may have installed an update since 10/29/2021, that file apparently did not change (it's dated 10/29/2021 on my machine as well even though I have updated since then). The date of the file isn't updated when you publish a project, it just gets copied over to your publish folder from the installation folder.
The issue you're experiencing, "...it is stopping the file from updating to the changes," is likely being caused by something else. Can you explain in more detail what isn't "updating to the changes"?
I have a file that is in our CRM from a project. I updated the project in Storyline and published. When I move the file into the CRM the file doesn't update to the new version. It is because of the analytics file- all other files will update to the correct date of 11_11. .
I'm surprised the date of a file would cause such a problem. Have you tried uploading an older version to Scorm Cloud and then overwrite it with a newer version to see if the problem happens on that platform? If it doesn't, the issue lies with your CRM.
One way around it, if indeed the file date is the problem, is to extract the analytics file from the published zip, open the analytics file in Notepad and add a simple space at the beginning of a line (so Notepad recognizes the file has changed but the functionality of the code isn't changed) and then save the file and replace it in the zip. The file will have today's date.
Is the CRM displaying an error message when you upload the later version of your project indicating that the analytics file in particular (or any file in general) is out of date or date-mismatched? Or is it just that you do not see the updated content after trying it out on the CRM platform?
Sounds like something else is going on then. If you can do so, you might try deleting the old course from Canvas first, or leaving the old version but installing the new version under a slightly different course name.
It worked, I deleted older file and moved new one in. Sounds so easy, should have tried that first. Blahhh! Thank you SO much for working through this with me. I owe you one!
13 Replies
Anyone??
Julie,
What is the date of your analytics-frame.html file? I have the latest version of Storyline 360 installed and the date of the analytics file is 10/29/2021 even when publishing a file today (11/12/2021). The analytics file in the published folder is the same date as where it originates from: C:\Program Files (x86)\Articulate\360\Storyline\player\{classic or unified depending on the player chosen}
If you have Storyline up to date but the analytics file is much older, that does seem odd. If not, I'm wondering if there's something else going on with your project.
the analystics file date is 10/29/2021 and the html 5 and other was 11/11/2021.
I think you're all set then as far as the analytics file goes. As I noted, the analytics file is pulled from the Storyline 360 installation folder. Even though you may have installed an update since 10/29/2021, that file apparently did not change (it's dated 10/29/2021 on my machine as well even though I have updated since then). The date of the file isn't updated when you publish a project, it just gets copied over to your publish folder from the installation folder.
The issue you're experiencing, "...it is stopping the file from updating to the changes," is likely being caused by something else. Can you explain in more detail what isn't "updating to the changes"?
I have a file that is in our CRM from a project. I updated the project in Storyline and published. When I move the file into the CRM the file doesn't update to the new version. It is because of the analytics file- all other files will update to the correct date of 11_11. .
I'm surprised the date of a file would cause such a problem. Have you tried uploading an older version to Scorm Cloud and then overwrite it with a newer version to see if the problem happens on that platform? If it doesn't, the issue lies with your CRM.
One way around it, if indeed the file date is the problem, is to extract the analytics file from the published zip, open the analytics file in Notepad and add a simple space at the beginning of a line (so Notepad recognizes the file has changed but the functionality of the code isn't changed) and then save the file and replace it in the zip. The file will have today's date.
Ok, I will try these things. Thanks for responding, I appreciate it.
Is the CRM displaying an error message when you upload the later version of your project indicating that the analytics file in particular (or any file in general) is out of date or date-mismatched? Or is it just that you do not see the updated content after trying it out on the CRM platform?
It moves over to the CRM, but then when I check it in Canvas, it is the older version (the initial project) rather than the updated project.
Sounds like something else is going on then. If you can do so, you might try deleting the old course from Canvas first, or leaving the old version but installing the new version under a slightly different course name.
Ok I'll try that first. Thanks!
It worked, I deleted older file and moved new one in. Sounds so easy, should have tried that first. Blahhh! Thank you SO much for working through this with me. I owe you one!
Thanks for letting us know you got it sorted out, Julie. Have a great day!