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
Hey,
it sounds like your db/ connectionstring needs to be configured properly.
What db are you using and how it the db server hosted?
How does the connection string look like and how is the db configured?
Please share as mucch information as you can - without sensitive information.
Kind regards Jack
Hey,
your foreign key probably does not prevent deletion because your customer entity has soft delete enabled. That means the record ist still in the db after you delete it and the foreign key stays intact.
Depending on your architecture, you can either fire off an event and prevent deletion somewhere, or guard against deletion inside of the appservice which deletes the customer - for example by checking the order repository for existing entries on the customer to delete.
You may take a look at ABP's free DDD e-book for inspiration on Implementation.
Long story short, you just need to ensure that your data stays consistent inside your code. Implementation needs to match your specific requirements and architecture.
Please let me know if that helps.
Kind regards Jack
Yes, that is the one I was thinking of, I registered but could not attend at the time. Was it recorded, is there a way to watch it?
Sure, log in to kommunity using the account which is holding the ticket. Then, navigate to this link of the conference: https://kommunity.com/volosoft/events/1st-abp-conference-96db1a54/talks
Go to "Talks" and you can watch the recordings
Kind regards, Jack
hai liming, thanks for your response.
I don't want to use two sets of package as it is unnecessary and will increase the download time.
can you please confirm if I can use the LeptonX Blazor server theme without the Blazorise package?
Hey Andy,
you can not use lepton/ leptonx UI without blazorise, as the UI is build with that.
If you want to remove blazorise, you have to create the UI completely on your own.
