Activities of "maliming"

hi

You can override the PublishEventsForChangedEntityOnSaveChangeAsync of AbpDbContext and skip these lines.

if (entityEntry.State == EntityState.Unchanged)
{
    ApplyAbpConceptsForModifiedEntity(entityEntry, true);
}

I will add an option to skip this in the next version.

hi

Can you try to use a new database name?

Thanks.

You can consider handling concurrent exceptions rather than disabling them. You can catch exceptions and then retry.

hi

We can only modify the code to resolve this issue. There is no simpler way.

hundreds of entities

Only entities with 1-n relationships may get concurrency exceptions. Not all entities.

hi

we implemented the solution for task type successfully.

Are you using IgnoredNavigationEntitySelectors?

hi

Get a token for the user in a SaaS tenant

How did you get the new token?

Please share your HTTP request

Thanks..

hi

Since the new version might have no direct relationship to the original entity, would this process still trigger an update to the concurrency stamp of the existing entity?

No, it will only trigger for the navigation property.

The OpenIdConnect will validate the OpenIdConnectOptions. So you have to set a value initially.

hi

Framework will skip it : https://github.com/abpframework/abp/blob/rel-9.1/framework/src/Volo.Abp.EntityFrameworkCore/Volo/Abp/EntityFrameworkCore/AbpDbContext.cs#L274

You can try it.

Thanks.

hi

abp update --version 9.1.1

Or

You can search and replace the abp & Volo package version in *.csproj files globally.

ABP & VOLO to 9.1.1 LeptonX to 4.1.1