Skip to main content
J
JEL888
Known Participant
December 30, 2016
Answered

Save Captivate cpvc files to SharePoint

  • December 30, 2016
  • 1 reply
  • 808 views

Hello,

Have found old forum and articles (2011) on this issue, but without resolution.  I assume that by now it's been solved.  If you want to save projects (.cptx and .cpvc files) to SharePoint (because multiple persons will be working on creating projects and need to save and later publish to one library) how is this done without getting the error message that an instance of Captivate is already using this file?

Here an old article that shows the same error I receive now: Discussion | eLearning | Page 784417

Has anyone resolved this?  Thanks!

    This topic has been closed for replies.
    Correct answer RodWard

    Agreed. 

    The error messages about the project file already being used by another person will NOT be an issue if all you do is use the Sharepoint site to be the backup location for CPTX or CPCV files that have been copied up to that location AFTER having been saved and closed down locally on the developer's own hard drive.

    While Sharepoint might be considered as a repository for storing backups of the project files, it doesn't usually end up being a good location from which to distribute the final published output to the end users.

    1 reply

    Paul Wilson CTDP
    Paul Wilson CTDP
    Community Expert
    December 30, 2016

    Adobe Captivate project files are not compatible with this type of process. Every time I have worked for an organization I have to download the latest copy of the file, work on it locally and upload it back to it's network location. Any time I have attempted to work on CPTX files from a network location, SharePoint or not, it always ends badly for that project file.

    Paul Wilson, CTDP
      RodWard
      RodWardCorrect answer
      Community Expert
      December 30, 2016

      Agreed. 

      The error messages about the project file already being used by another person will NOT be an issue if all you do is use the Sharepoint site to be the backup location for CPTX or CPCV files that have been copied up to that location AFTER having been saved and closed down locally on the developer's own hard drive.

      While Sharepoint might be considered as a repository for storing backups of the project files, it doesn't usually end up being a good location from which to distribute the final published output to the end users.

        J
        JEL888Author
        Known Participant
        December 30, 2016

        Thank you both for answering so quickly!  So if I understand correctly, if we work on our projects locally then via Explorer save the files in a SharePoint Library as backup that's fine.  But if we then open the backup files from the SharePoint location within Captivate (using Captivate's access to that folder), modify the project in Captivate and then save back to SharePoint (as before), this may corrupt the project?  So, that would mean I have to keep the working copies of all projects in a local folder (the default Captivate folder for example or one we create that speaks to everyone) and only use the backup copies for emergencies (putting them back into this local folder before opening in Captivate)?

        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices