Hi ABP Support Team,
While updating my "Transaction" entity, I noticed that ABP's auto-generated CRUD code removes my custom TransactionDeletedEventHandler. However, my other custom event handlers — TransactionCreatedEventHandler and TransactionUpdatedEventHandler — are not affected.
I suspect this might be because when ABP regenerates the DeletedEventHandler for the master entity, it searches for all files containing the term “DeletedEventHandler” and deletes them. This could have unintentionally removed my own TransactionDeletedEventHandler.
To confirm this, I renamed my file from TransactionDeletedEventHandler to TransactionDeleteEventHandler (removing the last “d” in “Deleted”), and after doing so, ABP no longer deletes the file during code regeneration.
Could you please help me check if this might be an issue?
Thank you!
Hi,
When using ABP's auto-generated CRUD API, I noticed that for a child entity, a GetListAsync endpoint is generated, and its input DTO includes the master entity's ID. However, the GetListAsync API does not actually use the master entity's ID to filter the data.
I’m aware that ABP also generates a GetListBy<MasterEntityId>Async method, which does perform the filtering, but I still find it odd that the generic GetListAsync includes the master ID parameter without using it in the query.
Here’s an example from my project: I have two entities: PurchaseOrder (Master) and PurchaseOrderChange (Child).
The PurchaseOrderChange input DTO for GetListAsync (In AppService) includes the PurchaseOrderId (Master Entity ID):
However, the GetListAsync (In Repository) method does not use PurchaseOrderId to filter the results:
Is this the expected behavior by design? Or is there a configuration I’m missing?
Thanks in advance!
Hello,
When I creating a Child Entity’s Child Entity in ABP Studio, I can select another Child Entity as the Master Entity for the new table. However, after clicking Save and Generation, the generated code throws an error.
The issue is that the generated Master Entity .cs file does not include a navigation property for the newly created table. As a result, when establishing the one-to-many relationship in DbContext, it fails due to the missing reference.
To resolve this, I have to manually add the navigation property in the Master Entity's extended file.
My question is: Does ABP Studio not support creating a Child Entity’s Child Entity by default? Or is there something I can do to prevent this issue from occurring?
