You are viewing limited content. For full access, please sign in.

Question

Question

User receiving a prompt to reload a document before it may be modified

asked on March 19, 2015 Show version history

The user is receiving a Laserfiche warning message

This document has changed on the server, and must be reloaded before it may be modified. Do you wish to get the latest version now?

I have not seen any documentation on this warning message within the support site.

Could you please explain the warning message?

Wondering if this message is related to Version Control or if this message could be the result of a larger issue?

0 0

Answer

SELECTED ANSWER
replied on March 19, 2015

In general this message happens if multiple people are working with the document at the same time. If you and I opened the same document and then you made changes to it, when I went to start modifying the document it would ask me to reload - that way it would have the version with your changes and we wouldn't possibly run into a conflict of trying to save two different renditions at the same time. The 'version' in this case really just means that slightly more newer version with your modificiations - it doesn't directly tie into Laserfiche versionining (it could be a new version there too, it doesn't have to). 

2 0

Replies

replied on March 19, 2015

Which version of the client are you using? There were a couple similar bugs that have been fixed in 9.1 and 9.2.

0 0
replied on June 23, 2016

Would you please point me to the bug fixes?  I'm running 9.1.0.413.

 

I have a situation where two people are logged into Laserfiche on the same computer.  This is needed because both need to sign a folder with their signature field.  They get the following error

 

And it becomes an endless loop because it never just reloads and lets them go on.

Thanks,
Sandy

0 0
replied on June 23, 2016 Show version history

The latest hotfix for 9.1 is version 9.1.1.584 which can be downloaded here, try updating and see if that fixes the problem.

Edit: fixed the link

0 0
replied on January 25, 2017

I have a user who is getting this error message; but has the latest hotfix, 9.1.1.584. Any other ideas? 

Thanks!

Julie

0 0
replied on January 25, 2017

Do you have workflows running that could be modifying the document?

0 0
replied on January 25, 2017

The only thing that would be running on it is a Starting Rule that I added to the workflow to detect for a user change on a document to start the workflow. But if a user is in a document updating metadata fields, the change event should only fire when the user closes/saves the document, right?

0 0
replied on January 25, 2017

The starting rule would be triggered if the user saves their changes before closing the document (in the document viewer, not the metadata dialog).

0 0
replied on January 26, 2017

Right ... the user is not saving it in the middle. Only making her updates and then "X-ing" out of the document.

0 0
replied on January 26, 2017

Please open a support case so we can look into it further.

0 0
replied on January 27, 2017

Will do although have another question since I'm fairly new to this all. We do have a workflow that has a wait step in it for one piece of metadata (PO#). Could a wait step potentially be vying for control over a document? The wait step only checks that the PO# is not empty.

Thanks,

Julie

0 1
replied on January 30, 2017

I've tried to make some workflow adjustments guessing what the issue could be; but we are still getting the error.

How do I go about opening a support case?

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.