Red Hat Bugzilla – Bug 1275359
Force Unlock works in unexpected way
Last modified: 2016-02-09 12:06:51 EST
Created attachment 1086549 [details]
Force Unlock behaviour
Description of problem:
If you trying to Unlock some Business Process and then modify it after Saving you will have last state of previous modification by another user.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open Business Process by user A and make some changes without saving
2. Open the same Business Process by user B and Force Unlock this Business Process
3. Make some changes by user B
4. Click Save button by user B
User B will commit state of user A not his own. See attachment.
User B will save his own changes.
Update: It seems like Business Central will save both versions: from user A and from user B but commit from user A will be the last one. So it will be opened like actual version, but you can to restore version from user B through Overview tab.
When user B commit changes and will try to make some more changes Business Process will be reopen and user B will see version from user A. And that's really confusing thing especially if you don't know that "Latest Versions" has your work also.
P.S. Still valid for 6.3.0 DR1