Prevent users from being able to delete features

Question

Hello All, 
 
 Any suggesting on best way to prevent users from deleting spatial features accidentally? 
 
 I created a trigger in the database that looks at a column Lock_Status and if Locked is True, then the user is unable to delete the record. This works and prevents the users from deleting the records from OpenCities Map. The issue I have is if users selected a mix of features where some have Lock_Staus = Ture and others = False, OpenCities Map throws a Posting error (for the ones that cannot be deleted) but stops processing and will not delete the ones that can be deleted. 
 
 Whole reason for this is that despite training, there are still people who are locking all features for editing and do not realise they are deleting features or accidentally delete features they meant to edit. 
 
 Regards, 
 Tanya Geldenhuys 
 
 .

Kees van Prooijen [Bentley] · Accepted Answer

I have 2 remarks: With a spatial post, when an error occurs the post process will not stop when you enable the checkbox "Continue On Error". Or with a key-in use: Gdi Post continue=true . (see the online help https://docs.bentley.com/LiveContent/web/OpenCities%20Map%20Help-V15/en/GUID-F51E13EC-FE1E-48D8-9DD8-A8CE36A4E68D.html ) Another option is to lock a level via the Level Manager. When a level is locked in the Level Manager, s patial features can be queried successfully, but a spatial lock on these features is not possible (neither is a spatial erase).

Prevent users from being able to delete features

Top Replies