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 DeleteEvent
object in the filter of the Backup job.
This can be added by going to the Included data tab. Then select Edit
> Manually configure
.
How to include Delete Event object in your Backup job
On the dropdown menu under "Show" click on Not Recommended Objects and search for DeleteEvent
object.
β
Once done, click on Save
to make sure your selection will be applied.
A short video to demonstrate:
To confirm the change was made correctly, you can click on Selected objects dropdown option and search for DeleteEvent
object on the list of selected objects.
β
What does including DeleteEvent object allow Gearset to do?
This will allow Gearset to see and track the deletion on records. Once added, future runs of your backup job will show who deleted the record. This is shown on the record in the job run details.
β
From the Data backup jobs page, for the Backup job in question click on Job history
, and 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 backup 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 object 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 the 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.