In case you need to consider other users, or processes working on the same project, please lock as little of the project data as possible. The project is locked by default, when it is opened or created using the respective methods OpenProject Also getting the selected project by the method GetCurrentProject SelectionSet class, will lock the project completely. If you don't need to mind multiple-user issues, e. This low-level type of locking can be used concurrently with 'automatic' one or as the only locking. Apart from automatic locking mechanism there is also possible to call locking methods directly on required objects. Please use them only in exceptional cases, i. In rare cases however it may be necessary to switch off creating LockingStep manually or automatically. This guarantees that objects are released, even if an exception was thrown inside the block. The LockingStep class remembers all locks set during its lifespan and releases them when the LockingStep is being disposed. There however is no Unlock method in any DataModel class. When there is necessary access to some resources and the LockingStep is not created, an exception will be thrown NoLockingStepException. There are 2 ways of creating this object. This way is recommended in case of necessity to lock as little as possible and is not clear which objects need to be locked to perform a change.Īfter the SafetyPoint block, please call Commit method, otherwise the changes are rolled-back. Automatic means that they are locked internally before any change and unlocked after disposing SafetyPoint.

The mechanism is enabled since creation and until disposal of a SafetyPoint object, so the recommended way is to use it with using keyword. SafetyPoint class provides automatic locking of DataModel objects. Please take into account that API locking only wraps P8 locking techniques. If even this read-only access is not possible, we speak of an 'exclusive lock'.

Locks are one way of enforcing concurrency control policies.

Eplan demo