Control before deletion (action)

English Forum
1

Hello,

I would like to perform a check when deleting a record (click the deleted button on the form).
Except I haven’t seen anything like onDelete or anything else, can you tell me how this is done?

Please.

PS :
I saw a canDelete but I would like to be able to make a request in db to check if there are links with other objects before authorizing the deletion

2

Hello,
You can override remove method.

3

Hello,

I did not find this method? do you have his name?

Thanks for your answers.

4

Hello,
Try like this

2 « J'aime »
5

i’m thinking about it, I’m new to development, but the idea in my mind is that when a user wants to delete a record, its just make inactive. then we can check these records through the database or do a complete cleaning.
please let me know your answer so that I can improve myself if I have a mistake as an idea or if it is open to improvement.
best regards

6

could listeners be the solution ?

7

Hi ple-essieux,

Thanks for your help

I just need to create my own packages and extend my entity’s class repository ? The code you show is already in AOP, it’s for an object that I created that I want to overload the delete button to add controls before deletion.

8

Like @AxelorTeam said, you can overide the remove function in the dao/repository so you can edit this to inactive rather than deleting. For this, you have to create a new class, extends from the repository and bind it in the module file.

9

WOW it’s starting to get tense lol the dao package is a self-generating package, I have to create my own packages in the java source directory? do you have an example please?

10

When I develop, I use my own package because I use custom module.
I create a module like this : https://github.com/PHPierrre/Axelor-IntelliJ-Views-Hot-Reload
and I configure it with settings.gradle and build.gradle at the root of the axelor project

11

So I too create my own modules under eclipse, however when you create your DOMAIN XML files it generates the repositories even if you have a custom module, that’s where I’m lost… I hope I got it right Explain.

12

Yeah when you create new domain, it create new repositories.
If you want to add properties to extistant domain, you have to create a domain file in your own module and set the exact name and package that the axelor domain which already exist.

Initial Invoice domain : https://github.com/axelor/axelor-open-suite/blob/a9e63e788c6d038baceae8685d1bb8d42d522333/axelor-account/src/main/resources/domains/Invoice.xml

Add a propertie named contract to Invoice domain : https://github.com/axelor/axelor-open-suite/blob/8edf28ff533c6a908e4688d250c911d9709c96bc/axelor-contract/src/main/resources/domains/Invoice.xml

13

Hi PHPierre,

Yes I know that, but we are just talking about the .xml in the « domain » package, this will generate java classes in the build/src-gen/java package like:
« com.axelor.apps.group.db .repo »
with class repositories in it.

I can’t modify these class to add my overload

@Override
public void remove(BankReconciliation entity) {

like your example above because these files are generated.
How do I do it ?

Thanks for your help.

14

I am sharing the gist, where you can see the method of catching domain object before removal

I have used the entity listener method, where I can catch any events, you can see further events here

https://docs.axelor.com/adk/5.4/dev-guide/models/models.html#entity-listeners

1 « J'aime »
15

Ok the call works well, however how do I cancel the delete action, I saw that you are rolling back from an exception. I would just like to do a test and if the test is good I don’t do the deletion. How can I do this?

16

I have not tested that part, jpa entity listener can help. @SQLDELETE and @Where clause of those can be helpful