Tracking user who has deleted the record in the archive table
It is now possible to capture who deleted a record in a table with standard archiving and user tracking using attribute rules.
It is not possible to capture the user editing the data into the same table (as the row just gets ended).
It is possible to capture deletes into separate logging table.
Note this is an old screen capture, the Field should exist in your table that is being tracked. It doesn't matter which one, it is not being modified, it just needs to exist so that a calculation rule can be triggered on delete to place a record in the logging table.
There is no point in having a column called DeletedByfield within the table being tracked, as it is not possible to populate the result into the edited table during a delete.
Here is the arcade expression for the attribute rule:
return {
//we want to just return the value of field `Field` no change require
"result": $feature.DeletedByUser,
//this keyword indicates an edit that need to happen, its an array since we can make many edits
"edit": [
{
//the other class we want to edit
"className" : "GIS.CCC.TestDeleteLog",
//the type of edit, in this case we want to add so we say `adds`, its an array since we can make many inserts
"adds" : [
{
//the attribute of the feature we want to add,
// we only want to populate the pointGuid with the globalId of the feature being created
"attributes":
{
"FeatureName": "TESTDELETEUSERTRACKING",
"FeatureObjectID": $feature.OBJECTID,
"FeatureGISID": $feature.OBJECTID,
"DeletedBy": GetUser(GetFeatureSet($feature)).username,
"DeletedAt": Today()
}//,
//we want to use the buffered geometry to insert the polygon
// "geometry": none
}
]
}
]
}
