Question

Track Changes and Versioning

Updated May 5, 2017

asked on May 3, 2017

We have a client that uses the track changes feature inside of MS Word and is seeing something weird.

They open a document from their local drive, enable track changes, make edits and then save it to Laserfiche using the LF Office Addon. It then gets put under Version control in the repo. When the user goes into the Repo to open that document and enables the track changes again there is nothing there (it's not showing the changes prior to entering the Repo).

If they save this document into the Repo first and then make their edits it works just fine. Is this how this should be working?

Thanks in advance!

0 0

Replies

replied on May 3, 2017

That's a bit strange. Based on how you described it, the moment the client opens up the document in the repository, he should be able to see the MS red-line changes made prior to the repository save.

The only thing that won't be there are version comments in the metadata of the document because those are comments maintained by the Laserfiche system. On the initial import, the system will show it as a brand new document with no version history.

0 0

replied on May 3, 2017

That's what I would think, but it looks like from the Import from the local drive to LF it is treating the document as brand new in every sense and losing the changes that "Track Changes" is supposed to have.

0 0

replied on May 4, 2017

Hi Alex,

I'm curious--was the local document saved locally from the repository, or is it a document that's never been in the repository?

I was unable to reproduce the issue on my end. I created a new Word doc, typed in some text, turned on Track Changes, made some changes, and saved to the repository via the LF Word plugin. I started tracking document version on the folder in which I saved the Word document. I opened the doc by double-clicking it in the repository. It opened and all tracked changes were still intact.

I hope you're able to get to the bottom of this--please let us know what the problem was when you figure it out!

Thanks,

Rob

0 0

replied on May 5, 2017

It was a document never saved to the repository. So this doc was just on the users desktop. Let's say they worked on it for a day before finally deciding to upload to the Repository. When they save it to the Repo and then open the document up the changes are now gone.

0 0

replied on May 5, 2017

Hmm... Well, I'm sorry to say that I don't have any suggestions. The process you describe is exactly what I followed when attempting to reproduce the problem, which I wasn't able to do. Good luck!

0 0

You are not allowed to follow up in this post.

Question

Question

Track Changes and Versioning

Replies

Sign in to reply to this post.