Accepted Solutions
If you have cloned Products, after product export, you might notice a field called "Version_Optimized_Lock" as below -
Version_Optimized_Lock is an internal field used for version control.
For example, if user A and user B are both editing a Product, and user A saves his change -
In this scenario, Version_Optimized_Lock is incremented by 1, for example, from 2 to 3.
If user B decides to save his change at this point, he will not be able to because he is still on version 2. To proceed, user B will need to refresh the copy he's trying to make change to.
Version_Optimized_Lock is not used for, or affecting your daily operation.
If you have cloned Products, after product export, you might notice a field called "Version_Optimized_Lock" as below -
Version_Optimized_Lock is an internal field used for version control.
For example, if user A and user B are both editing a Product, and user A saves his change -
In this scenario, Version_Optimized_Lock is incremented by 1, for example, from 2 to 3.
If user B decides to save his change at this point, he will not be able to because he is still on version 2. To proceed, user B will need to refresh the copy he's trying to make change to.
Version_Optimized_Lock is not used for, or affecting your daily operation.
