@NAVAKANTHM

I'm not aware of any solution to this with the standard auditing features. There are lots of posts asking this question but no solution.

Declare Trigger rules should run when deleting instances (according to the documentation - https://docs-previous.pega.com/application-development/86/declare-trigger-rules).

So you should be able to implement an audit for deleting data (but note that if you delete a data instance, standard history reports won't be able to join the history to the data table using the key).

There is an alternative solution you can do which would solve the issue, but might not be ideal for your application:

Prevent users from deleting data instances through the security model.

Instead of deleting, add a Status/Deactivation column to the data type. If the user sets the status as deactivated then this should be filtered out of all results in your application as if it were deleted.

This way you can audit the changes to the status column.

Alternatively you might be able to implement your data as custom rules, this would enable the full rule auditing which includes deletion.