With a Data Backup job in Gearset you are able to see who deleted a specific record. To do this, you will need to include the Delete Event in the filter for this Backup job. This can be added by going to the Backup job settings, and then the Filtering tab.
This will allow Gearset to see and track the deletion on records. Once added, future runs of this backup will show who deleted the record. This is shown on the record in the job run details.
From the Backup Dashboard, find the backup run with the deleted record you are interested in. Then click View changes and View records to find the record you are looking for. You can also use the Search tab to find the record you are interested in.
When viewing the changed/deleted records, clicking on the specific deleted record will allow you to see who deleted this record in the DeletedBy field.
Why is DeleteEvent not a recommended object?
The DeleteEvent object is a very high frequency audit object. The repercussions of this are:
Extra time taken for each backup run.
Makes the backup overview much less clear. For example, it can be really hard to spot 100 account deletions when there are over 1000 delete event additions in the same run.
It is also an object that cannot be restored or deleted.
Why can I see deleted event history even though I haven't included DeleteEvent in my filter?
If you have noticed in some of your job runs that you're able to see the deleted history information without including DeleteEvent in your filter, then don't worry - this is to be expected. Gearset will provide that information for 15 days since that job ran, and then beyond that time window, that information will be gone. If you want to have that deleted information for longer - then you need to have DeleteEvent in your filter.
If you have any questions feel free to reach out to us via the in-app chat.