Add join table changes to a related entity's audit log history #8750

5 Answer(s)

• 

  0

  EngincanV created one month ago

  Support Team .NET Developer

  Hi, you can configure the entity history selector to conditionally log for a specific entity. Please check https://abp.io/docs/latest/framework/infrastructure/audit-logging#entity-history-selectors

  Regards.

  Save Cancel
• 

  0

  ben.shelton created one month ago

  Hello,

  I looked over the documentation that you sent and tried using the Audited attribute, but this did not give me what I was looking for.

  I am trying to manually add a history log entry to our User entity for changes that are not occurring in the User table. The changes occur on our UserAssignedMerchant join table.

  Here is some additional context on our User implementation:

  • We implemented our own User class and dtos, but are using IdentityUserManager calls that we adapted from source code to set the properties to still use the built in AbpUsers table and features in our create and update methods.
  • Also during those methods, we set the entries in the join table with repository calls for the join table.
  • We give the UserAssignedMerchant entries to the end users in a field that is a Guid[] called AssignedMerchantIds, but this only on the dto not the class so it's manually set at the time of retrieval.

  Is there a repository call (such as through IAuditLogRepository) that we can make to insert a history log on User that will allow us to manually set what changed in AssignedMerchantIds? Or is there a better way to accomplish this?

  Thanks.

  Save Cancel
• 

  0

  EngincanV created one month ago

  Support Team .NET Developer

  Hello,

  I looked over the documentation that you sent and tried using the Audited attribute, but this did not give me what I was looking for.

  I am trying to manually add a history log entry to our User entity for changes that are not occurring in the User table. The changes occur on our UserAssignedMerchant join table.

  Here is some additional context on our User implementation:

  • We implemented our own User class and dtos, but are using IdentityUserManager calls that we adapted from source code to set the properties to still use the built in AbpUsers table and features in our create and update methods.
  • Also during those methods, we set the entries in the join table with repository calls for the join table.
  • We give the UserAssignedMerchant entries to the end users in a field that is a Guid[] called AssignedMerchantIds, but this only on the dto not the class so it's manually set at the time of retrieval.

  Is there a repository call (such as through IAuditLogRepository) that we can make to insert a history log on User that will allow us to manually set what changed in AssignedMerchantIds? Or is there a better way to accomplish this?

  Thanks.

  Hi, you can configure the AbpAuditingOptions and define an EntityHistorySelector as below:

              opt.EntityHistorySelectors.Add(
                  new NamedTypeSelector(
                      "UserAssignedMerchant",
                      type => typeof(UserAssignedMerchant).IsAssignableFrom(type) 
                      ));
  

  Save Cancel
• 

  0

  ben.shelton created one month ago

  Hi, you can configure the AbpAuditingOptions and define an EntityHistorySelector as below:

              opt.EntityHistorySelectors.Add( 
                  new NamedTypeSelector( 
                      "UserAssignedMerchant", 
                      type => typeof(UserAssignedMerchant).IsAssignableFrom(type)  
                      )); 
  

  Hello,

  I implemented what you suggested, but I am not seeing a history record being created when I add or remove records from the UserAssignedMerchant table.

  For further context:

  • A record in the UserAssignedMerchant table consists of UserId, MerchantId, and TenantId
  • In the User Create and Update methods, we take the list of MerchantIds that are given to be assigned to the user in the respective dtos, then we create a record for each given merchant in the UserAssignedMerchant table if one doesn't already exist. Additionally, we delete records in the UserAssignedMerchant table that represent merchants the user no longer needs to be associated with.

  Save Cancel
• 

  0

  ben.shelton created one month ago

  Hello,

  I re-examined my implementation of your suggestion and realized it was not making the associated history log due to us using the bulk calls, InsertManyAsync and DeleteManyAsync, on the repository to add/remove records in the UserAssignedMerchant table.

  I was able to modify our existing CustomBulkOperationProvider to address this and now it does make history logs when a record in the UserAssignedMerchant table is created or deleted as we need.

  Thanks.

  Save Cancel