Reviewing locks

The system implements different levels of multi-user data handling to ensure each web request is handled securely, without any conflicts of data access and deadlock.

• Click <My Profile> | Administration | System | Locks. A list of the locks that the system is currently handling is displayed. There are three levels of locking:
  • A session lock is created when a user logs in and is maintained during the login session. It uniquely identifies the connection that the user has with the server. Any request that the user makes requires identification of the session lock. A request includes clicking a button, a hyperlink, or a contact name. Identification of the session lock is handled automatically, as each button and hyperlink generated by the system has the session lock built in.
  • Table locks and record locks prevent more than one user updating the same data at the same time. Record locks create a unique identification of the record that a user is accessing.
  • Locks work with ASP pages in Sage CRM. If more than one user is accessing a record by standard functionality or an integrated ASP page, each user is notified that another user is currently editing the record. You can switch this off using the CheckLocks property. For more information, see the Developer Help on the Sage CRM Help Center. When updating third party databases using extensibility features, the database administrator must ensure that a third party application and Sage CRM cannot update the same record at the same time.
• Click a lock hyperlink to review the Record lock fields.
• To delete the lock, click Delete.