Restrict non-iterated records to only allow one user to update at a time.

[jkent-2]

Non-iterated records allow more than one user to be in update mode for the same record at the same time. Iterated records (components like BOMs, Construction Sets, Measurement Sets), get 'checked out', but non-iterated records do not. This can cause data to be overwritten.

 For example:

1. User 1 opens a record in the Color library with the color name ‘Blue’. Currently the record has a date attribute that is null.
2. User 2 opens the same record.
3. User 1 enters a date in the date attribute.
4. User 2 leaves the date attribute as null.
5. User 1 clicks Save.
6. User 2 clicks Save.
7. The date attribute reverts to null.

This request is to restrict non-iterated records so that they only allow one user to update at a time, similar to how iterated records work. 

[olivierlp]

Hello,

We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.

You can always post a new idea with all the details required in the form.

Thank you for your participation.