Identity ABPUser synchronize problem because of Volo.Abp.Users.UserEto does not contains IsDeleted property #5234

8 Answer(s)

• 

  0

  Anjali_Musmade created one year ago

  Support Team Support Team Member

  Hi, can you share exact screenshot or steps to reproduce this issue?

  Save Cancel
• 

  0

  ElifKaya created one year ago

  Hi, can you share exact screenshot or steps to reproduce this issue?

  We have custom user entity(ModUsers). And we always listen to ABPUser table by using IDistributedEventHandler<EntityUpdatedEto<UserEto>>. And we aim to sync with our custom user data and ABPUser data in every cases.

  We can catch all changes in user creation and modification from ABPUser table. But, ABP make soft delete and marked as a IsDeleted column is true when user delete operation. But, Volo.Abp.Users.UserEto does not contains IsDeleted property so we can not catch a deleted user. It is not falling to IDistributedEventHandler<EntityUpdatedEto<UserEto>>. Because there is no IsDeleted property in your UserEto class.

  I shared the all necessary images above.

  Can you add IsDeleted property to your UserEto ?

  Save Cancel
• 

  0

  Anjali_Musmade created one year ago

  Support Team Support Team Member

  Hi,

  can you please handle EntityDeletedEto<T> is published when an entity of type T was deleted just like you have handled EntityUpdatedEto<T>

  Please see the documentation here https://docs.abp.io/en/abp/latest/Distributed-Event-Bus#event-types

  Save Cancel
• 

  0

  ElifKaya created one year ago

  Hi,

  can you please handle EntityDeletedEto<T> is published when an entity of type T was deleted just like you have handled EntityUpdatedEto<T>

  Please see the documentation here https://docs.abp.io/en/abp/latest/Distributed-Event-Bus#event-types

  Hi,

  ABP User Delete endpoint (api/identity/users/{id}) makes just a SOFT DELETE (not a Hard Delete). Actually, it is a update operation (not a delete operation). IsDeleted property is marked as a TRUE by ABP when we request to delete user endpoint.

  So it is not a delete operation and it is a update operation. We should not use a EntityDeletedEto<T>. We need to IsDeleted property in Volo.Abp.Users.UserEto.

  Also I tried using it as you said anyway. But as I said, this api/identity/users/{id} api does a soft delete operation, not a hard delete. Therefore, EntityUpdatedEto<T> should be used, not EntityUpdatedEto<T>. Therefore, I think that the isDeleted field should be added to Volo.Abp.Users.UserEto.

  

  

  

  

  

  Save Cancel
• 

  0

  Anjali_Musmade created one year ago

  Support Team Support Team Member

  Hi, Just for your information there is HardDeleteAsync method using which you can permanently delete the entity record from database. can you please check this link https://docs.abp.io/en/abp/latest/Repositories

  Here EntityDeletedEto is trigger when a delete operation is called, even if it is a soft delete it is an delete operation, if you want your moduser to have soft delete please read more on https://docs.abp.io/en/abp/latest/Data-Filtering#isoftdelete

  Here is a video showing delete triggers. Click Here

  Thanks,

  Save Cancel
• 

  0

  ElifKaya created one year ago

  Hi, Just for your information there is HardDeleteAsync method using which you can permanently delete the entity record from database. can you please check this link https://docs.abp.io/en/abp/latest/Repositories

  Here EntityDeletedEto is trigger when a delete operation is called, even if it is a soft delete it is an delete operation, if you want your moduser to have soft delete please read more on https://docs.abp.io/en/abp/latest/Data-Filtering#isoftdelete

  Here is the a snip showing delete triggers Thanks,

  Hi,

  Thank you for your example. Can you show me your delete api request, please? Because, we use "api/identity/users/{id}" this endpoint from ABP Identity Management. And, it doesn't trigger to EntityDeletedEto.

  I mean that, I don't want to hard delete or create another delete api. We just use a ABP Identity Management User Delete Action request. And I will continue to delete action from ABP Identity Management. So, Can you check your (api/identity/users/{id}) endpoint, please? Your user delete endpoint makes a soft delete.

  Or, Can you give an example by using your (api/identity/users/{id}) as you did above ?

  Thanks,

  

  

  Save Cancel
• 

  0

  Anjali_Musmade created one year ago

  Support Team Support Team Member

  Hi,

  Here you can see that this the same endpoint Click Here

  Save Cancel
• 

  0

  ElifKaya created one year ago

  Hi,

  Here you can see that this the same endpoint Click Here

  Thank you so much, I will try again :)

  Save Cancel