Avoid duplication and model shift when using Audit.net

[ektasinha-neuroflow]

I am working on using audit.net to keep track of changes made while saving and updating the data. I have been successfully able to do that. But there is a problem with my solution. We have multiple entities which need to be tracked separately in different tables. I created the separate audit tables with the same columns as the main table. For example:

public class User
{
  public required string Username { get; set; }

  public required string FirstName { get; set; }

  public required string LastName { get; set; }
  
}
 public interface IAuditEntity
 {
   public int AuditId { get; set; }
   public DateTimeOffset ActionDate { get; set; }
   public string Action { get; set; }
   public string? UpdatedBy { get; set; }
 }
public class UserAudit: IAuditEntity
{
  public required string Username { get; set; }

  public required string FirstName { get; set; }

  public required string LastName { get; set; }
}

It has successfully worked in tracking the changes for the entity but this way has led to duplication when creating audit classes. As more entities will be added and the changes would be made, the maintenance will be become cumbersome. Is there a way to avoid this with Audit.net?

[thepirat000]

I think the issue is that since you are using the default OptOut mode in Audit Entity Framework, all entities will be audited by default. However, you want to exclude the UserAudit or any audit-related tables. In this case, you need to explicitly ignore the audit entities.

One way to achieve this is by adding the [AuditIgnore] attribute to the audit entity classes:

using Audit.EntityFramework;

[AuditIgnore]
public class UserAudit: IAuditEntity
{
  public required string Username { get; set; }
  public required string FirstName { get; set; }
  public required string LastName { get; set; }
}

If that’s not the case, please share your configuration so I can provide further assistance.