Activities of "sserestyen"

Hi,

I don't have any CronExpression in my project, apart from the ones which comes with the pro packages. As I don't have access to its source code I cannot verify those.

What kind of workers and cron expressions do we have with the pro packages?

Thanks.

Hi,

Updating the project to 9.3.7. resolved the issue for setting the LastModificationTime value when only a foreign key is updated on the entity.

Thanks for your support.

[maliming] said: hi

I confirmed that the abp >= 9.3.7 will fix it.

https://github.com/abpframework/abp/pull/24104

Thanks

Hi,

Thanks for confirming the version with the fix included. We'll update the ABP packages to get that patch.

Thanks.

[maliming] said: hi

Does this solution work for you?

https://abp.io/support/questions/10057/LastModification-fields-not-updated-when-changing-one-to-many-relationship#answer-3a1d5bfa-d803-667e-e95a-7f8900a6abc8

Thanks.

Hi,

We didn't try that as the below note (copied from the other thread) indicated that it might cause issues later on: It seems to work with the given overrides. However, it's sad that by implementing these overrides we have the risks of possible missing feature updates and even future breaking changes.

Thanks.

It seems I cannot submit technical support related topics on https://abp.io/contact

Could you forward this request to ABP Support?

Thanks.

[maliming] said: hi

ABP soft delete actual do a update operator. So your OnDelete won't be called.

You can add an event handler EntityUpdatedEventData<IdentityUser> and check if IsDeleted is true or false.

Thanks.

Hi,

Thanks for your response on this. We'll look into these options.

Thanks.

Thanks for the clarification.

In our case, the Manager is deleted through the built-in Identity Management → Users page (i.e., the default user deletion flow provided by ABP).

Given that, how can we customize this flow so we can implement the following approach?

Override/customize the user deletion process in our application/domain service and explicitly update dependent entities (e.g., set Employee.ManagerId = null) before or after the user is soft-deleted.

What is the recommended way in ABP to hook into or override the built-in user deletion logic used by the Identity Management module so we can safely apply our custom logic when a user is deleted from the UI?