Activities of "digitalservicegb"

• ABP Suite Version : 9.1.0

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!

• ABP Framework version: v9.0.4
• ABP Studio : v9.0.4
• Database System: EF Core (SQL Server)

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).

1. The PurchaseOrderChange input DTO for GetListAsync (In AppService) includes the PurchaseOrderId (Master Entity ID):

2. 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!

I delivered your report to the ABP Suite team currently,

They'll investigate and fix it.

Hi,

I’d like to know if you are able to reproduce this issue. I want to confirm whether others might encounter the same problem as well.

Thanks!

I delivered your report to the ABP Suite team currently,

They'll investigate and fix it.

Ok Thank you!

Hi,

Unfortunately I couldn't reproduce the exact same issue.

Here some of questions to determine problem properly:

• Which version of ABP Suite do you use? (Also your ABP version)
  • 
  • 
• Did you add navigation manually in navigations tab? It should work without adding it
  • 

Hi

My ABP Studio and ABP Versions

• ABP Studio: 9.0.4
• ABP Framework: 9.0.4

My Case

I want to create a four-layer Master-Detail relationship.

• Creating the second-layer entity was successful since it's a typical case in the ABP documentation.
• However, when I tried to create the third-layer entity, the .cs file of the second-layer entity did not include a navigation property for the new table.
• In this case, the third-layer entity's master entity is the second-layer entity, while the second-layer entity is also a child entity itself.

Manually Adding Navigation in the Navigations Tab I tried to manually add the navigation property in the Navigations tab, but it showed an error message: "The master entity can not be same with the navigation property."

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?

• I can select another Child Entity as the Master Entity for the new table.
• The Master Entity’s .cs file does not include a navigation property for the new table.
• Causing DbContext to fail when establishing the one-to-many relationship.
• I need to manually add the navigation property in Master Entity's Extended file.

Thanks, the packages could now be restored.

Thanks for the update and your patience. Sorry again for the trouble.

nuget.abp.io is down!

Response status code does not indicate success: 503 (Service Unavailable).

Today is not a good day today.