Activities of "jfistelmann"

Hey,

to me it sounds like your answers may be solved by this youtube video from ABP YouTube ABP Framework Entity Framework Core

There it is described how to merge the dbcontext of different modules into one. Please watch it and tell me if you have any further questions.

Hey,

another shot in the dark: I took a look at the documentation and found this here

https://docs.abp.io/en/commercial/latest/modules/chat#adding-distributed-event-bus-for-distributed-architecture-projec

In your initial question, you said that your application is tiered - that's why I wanted to ask if you added a distributed event bus like described?

Hey, simple shot in the dark:

Make the DbSet full properties. You only have {get; } -> {get; set; } Guessing a DI thing based on that.

Let me know if that helped

Yes, I want to create a new tenant by inheriting all information from the clone source. how do i do that?

can you elaborate more on "all information"?

implementation varies on the specific definition.

for instance, you can just copy information on the tenant entity. do you want to transfer users as well?

are there entities that need to be copied as well?

are there any requirement that you copy created/ updated etc dates of any entities?

are there any requirements to store information about the source of where data has been copied from?

Generally spoken, you can do something like extending the tenant entity to store a source tenant. then, you could use DataSeeder's with the tenant filter disabled to perform the stuff you need.

Depending on your requirements, a background job may be a better fit, as copying data may take a while.

As you see - it all depends and the devil lies in the details.

As what we understand, on record deletion, it started showing the deleted record after applying this configuration whereas it should be deleted physically (hard delete).

We applied this configuration in Application project....Is this the right project?

Application layer is okay, better put it in domain layer to spread it accordingly.

To your concern: Docs indicate only the "read-changes".

I've taken a look into the code on github. To me it seems like you disable soft deletion completely by adding the code above.

Hey,

here it is: https://github.com/nebula2/abp-qa-5459

take a look at the app service here https://github.com/nebula2/abp-qa-5459/blob/master/src/Qa5459.Application/Entities/ParentEntityAppService.cs

Please note, that ensuring business logic consistency through foreign key constraints - and trying to handle such exceptions inside the application layer is most likely not a good practice.

we already solved this by adding MultipleActiveResultSets=True ,

i have another question , how to enable Hard Delete globally including implemented modules like (Saas, Identity ,etc..)

Happy to hear that,

You should be able to disable SoftDeletion globally following this here: https://docs.abp.io/en/abp/latest/Data-Filtering#abpdatafilteroptions

I have done as you recommended and it threw another exception:

I will create an example repo and share the github link. I think that would be best.

Hi,

that's probably because of the UOW.

try this:

await _productRepository.DeleteAsync(id, autoSave: true);

Hey Dharma,

You could throw a BusinessException or a UserFriendlyException.

Keep note that in your approach you would most likely need to override the DeleteAsync-method and wrap a try-catch around deletion of the entity, to then be able to even catch the FK-Exception.

kind regards Jack