Skip to main content
Solved

Error when trying to check-in a new revision

  • February 25, 2025
  • 6 replies
  • 45 views

Forum|alt.badge.img+10
  • Sidekick (Customer)
  • 50 replies

I am getting the following error when trying to check-in a new revision.  We updated all our SOP’s to a new format.  The old file type was DOCX. We are now at a .DOC filetype.  I get the error below.  If I change it to the DOCX file type, it works.  Why is this and is there a workaround???

 

Best answer by Mathias Dahl

Can you share some screenshots? If you create a new revision of a document that had a .doc file checked in, you will get a copy of that in the new revision if you select to copy the file (if not, no file is copied). If you then want to change the file type, we don't really have a convenient way of doing that. You then need to get a copy of the new revision (by using View or Copy File To...), then delete the file from that revision, then upload the new file (.docx).

If you tried to Edit the revision that has a .doc file, and check it in using a .docx file, it might fail, since it's a scenario I don't think we have code to handle.

 

View original
Did this topic help you find an answer to your question?

6 replies

Mathias Dahl
Superhero (Employee)
Forum|alt.badge.img+32
  • Superhero (Employee)
  • 2857 replies
  • February 26, 2025

The error doesn't sound like it has anything to do with file types or file extensions, but who knows... Can you try these things:

1. Try uploading a .docx file instead - does it work?
2. It looks like the File Storage repository type is used in Docman, can you temporarily try with the Database repository, perhaps for some dummy document class that you can test with?

By the way, did you really change from DOCX to DOC? People usually do it the other way around, considering .doc is a quite old extension now…

 


Forum|alt.badge.img+10
  • Author
  • Sidekick (Customer)
  • 50 replies
  • February 26, 2025

Yes, my apologies, it was from DOC to DOCX.

So, original document revision was a .doc file.  Two revisions after that were .doc files.

We have updated our templates and documents to DOCX.  I tried uploading it as a new revision and get the error.

I open and resave it as a .doc file (1997-2002) and it works.


Mathias Dahl
Superhero (Employee)
Forum|alt.badge.img+32
  • Superhero (Employee)
  • 2857 replies
  • Answer
  • February 26, 2025

Can you share some screenshots? If you create a new revision of a document that had a .doc file checked in, you will get a copy of that in the new revision if you select to copy the file (if not, no file is copied). If you then want to change the file type, we don't really have a convenient way of doing that. You then need to get a copy of the new revision (by using View or Copy File To...), then delete the file from that revision, then upload the new file (.docx).

If you tried to Edit the revision that has a .doc file, and check it in using a .docx file, it might fail, since it's a scenario I don't think we have code to handle.

 


Forum|alt.badge.img+10
  • Author
  • Sidekick (Customer)
  • 50 replies
  • February 26, 2025

We are just starting to use Document Management and still learning the ins and outs.

With some testing, I noticed that we Creating an New Revision, in the assistant, you can select whether to bring the old file over.  Toggle this off and then there are not issues.

I was bringing the old file over, checking it out, and then trying to upload the new file format.

Thanks for the help!!!!


Forum|alt.badge.img+10
  • Author
  • Sidekick (Customer)
  • 50 replies
  • February 26, 2025

 


Mathias Dahl
Superhero (Employee)
Forum|alt.badge.img+32
  • Superhero (Employee)
  • 2857 replies
  • February 28, 2025

@TTRACY 

Thanks for trying that and reporting back, glad to see you solved the problem.

As a side note: it would not be impossible to allow what you tried to do, but it's not a clear cut good idea either. If the user is selecting a file with another file type/extension when they check in, we cannot know for sure if it's on purpose, or not. So we would need to ask, and this will further complicate the solution and possibly the user will anyway click "Yes, I want to do this", thus possibly overwriting the file in the repository with a wrong one.

I do think the error message should have been a specific one instead though, telling what the problem is. Feel free to file a support case about this and we can have a look at making it better.

Have a nice weekend!
 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings