Question

Office integration with desktop repository client automatic check out

Integrations Version 12

Updated February 6

asked on January 15

Hello,

Since we upgraded from Laserfiche version 11 to version 12, we have noticed that the document locking process for Office suite files has changed. In version 11, a document was locked when opened and unlocked upon closing. Now, with version 12, it seems that this process has been modified to perform a document checkout when opening and checkin upon closing.

We have encountered issues with some users who work with multiple documents open simultaneously. When they close a document, the checkin process does not always complete automatically. I do not have an exact procedure to reproduce the problem, but this can lead to confusion for the user. When they try to access the document again, they receive a message indicating that the document is still checked out. This could eventually result in modification lost if the user clicks Yes on that prompt.

To avoid losing modifications, the user must select No. They then need to manually cancel the document checkout. After that, they can reopen the document. A message will appear indicating that a version of the document was found on the workstation. The user must select that version to preserve their changes.

Is this a known issue?

Thank you

0 0

Answers

APPROVED ANSWER

replied on February 4

The latest Office Integration includes fixes for "A checkout lock issue for versioned Office documents opened via the Web client's Download and Check Out or Edit With options" (includes fixes for bug #s mentioned above).

Download link: KB: 1014488

1 0

SELECTED ANSWER

replied on January 16

We have seen the same for several customers who have upgraded to LF12. For now we have stopped rolling out the LF12 Desktop Client and only upgrade the server side components to mitigate against unsaved changes. If it is the same issue then the bug number is 616562.

2 0

View 4 previous replies

replied on January 16

Hi Nigel,

Thank you for the information. Unfortunately, I don’t seem to be able to access bug number 616562. Could you please provide more details? Also, has this bug been taken care of and will it be fixed soon?

Thank you

0 0

replied on January 16

I think bug numbers are for Laserfiche internal use only so wouldn't appear until the corresponding issue is resolved and listed in the release notes. I don't know anything more on a release date though I'm afraid.

2 0

replied on January 19

Confirming the bug numbers are for Laserfiche's internal use. However, fixes listed in the public release notes often indicate a related bug number after them, like:

$DescriptionOfFix ($BugID)

I checked on this specific issue and found that the original bug filed as 616562 was merged into a new item with ID 630875. It's filed as high severity and priority, and it appears the dev team is actively working on a hotfix. That suggests it'll be fixed sooner rather than later.

@████████please have your Solution Provider open a support case for this issue, referencing this Answers post so we can confirm if it's the same issue and if it is, so you can be informed through official channels when the hotfix is available.

0 0

replied on January 19

Hi Samuel,

I spoke about the situation with our reseller this morning. They should be opening a ticket related to this post and the bug 616562.

Thank you

1 0

APPROVED ANSWER

replied on February 4

Download link: KB: 1014488

1 0

replied on February 6

Hi Paolo,

Thank you for the information. However, as mentioned earlier in the discussion, this issue is related to the desktop repository client and not the web client. In addition, the bug number mentioned by Nigel does not appear to be fixed in the KB you referred to.

0 0

replied on February 6

Hi All,

Bug 616562 which is specific to the desktop client (for both cloud and self hosted systems) has been logged for this issue and is still outstanding. The latest office integration 11.1.2601.902 is for the web client only. There is no ETA for when or if bug 616562 will be resolved.

Hope this helps clarify.

Cheers!

Chris

1 0

Question

Question

Office integration with desktop repository client automatic check out

Answers

Replies

Sign in to reply to this post.