[yazilim.ithinka] said: Has the issue been resolved? I had used this link https://abp.io/support/questions/8627/Install-specific-version-of-ABP-Studio and then I downgrade abp studio, suite, cli version but I had taken angular cannot get error. Please resolve this issue or provide installation instructions for working versions and how to proceed. This issue is disrupting our work at Abp.
Hi, we've fixed the problem but haven't released a new version yet:
Currently, the best thing you can do is to manually fix the controller namespace or update the related templates. I suggest the first approach, you can open the relevant controller and add the required namespaces, and delete the wrong namespace:
- using ClassifAI.ManagementService.Shared;
+ using ClassifAI.ManagementService.Services.Categories;
+ using ClassifAI.ManagementService.Services.Dtos.Categories;
+ using ClassifAI.ManagementService.Services.Dtos.Shared;
Also, you need to update the namespaces in your *Control.Extended.cs file.
[yazilim.ithinka] said: Has the issue been resolved? When I checked today, the same error still persists.
Hi, no, currently it's not resolved. We will try to fix it asap.
Hi, thanks for the suggestion. You are right, we should also add HandleErrorAsync for the delete methods. I'll make the related changes, thanks.
Regards.
[48949912] said:
[EngincanV] said:
[48949912] said:
[maliming] said:
I will forward to our suite team.Thanks.
Excuse me!
How to Resolve this problem?Hi, the problem you stated is a known problem and we will fix it soon. In the meantime, the only possible solution is to fix it in the generated code. So, manually delete the related line in your automapper class for now.
Excuse me! How long will it take to fix? The project is urgent. Manual modification is possible, but it's a bit tedious and will require extra time.
We have an open issue for this problem and will try to fix it asap, but unfortunately, we can't give an exact time for now.
[48949912] said:
[maliming] said: I will forward to our suite team.
Thanks.
Excuse me! How to Resolve this problem?
Hi, the problem you stated is a known problem and we will fix it soon. In the meantime, the only possible solution is to fix it in the generated code. So, manually delete the related line in your automapper class for now.
[rafael.gonzales] said: Hello @EngincanV.
Sure. I will send you the demo project. Is it possible to calendar a meeting and show you the issue directly?
Hi @rafael.gonzales,
Thanks. Please send me the demo project first so I can check and try to reproduce the issue. If I’m not able to reproduce it on my side, then we can schedule a meeting to review it together.
Hi @rafael.gonzales, I'm unable to reproduce the problem. By any chance, can you please send your project via email to support@abp.io (with ticket number)?
[lucasconde] said: Hi, could you please elaborate if this will be supported by ABP Suite at some point and what is the timeline?
We are starting a huge project and need to define the way to move forward, although the document states that, it might be actually feasible to do some adjustments.
Hi @lucasconde, when you add your microservice to the Suite, it writes its details to the appsettings.json file under the .suite folder (%%user-profile%%/.abp/.suite). You can see all of your solutions there, and you can change the DomainProjectDirectory and other directories and general options to let ABP Suite generate the code in the relevant directories with options:
Unfortunately, currently, there is no option in ABP Suite to do it on the UI side. So, you need to do it manually.
Regards.
[daniel.meza2011@outlook.com] said: Hi, thanks for the clarification, the thing is that data is been stored in a separate collection and not inside the same document in case of mongo, I know that for SQL db that is a must (ef has ways to put it as a collection in the entity, but still data is in a supérate table).
So I would like to see just one approach in mongo db projects, or perhaps have the ability to decide which approach use, I think the easy path here is just remove the ICollection from the Master entity.
Hi, actually we can easily remove the ICollection<> from the master-entity and it works as expected without effecting anything for MongoDB. I'll make the related change, and it will probably be included with v9.3.2.
Regards.
[daniel.meza2011@outlook.com] said:
The current behavior is a known limitation, and the recommended approach is to use only one pattern (reference) for MongoDB master-detail relationships in ABP Suite.
This is not clear, the documentation just states that Repository, Manager and AppService are created. Not a single mention to this issue.
Hi, thanks for pointing this out, and sorry for the confusion caused by the AI-bot’s initial response. You are right, Suite currently mixes two different modeling styles for master–child relations in MongoDB.
At the moment, ABP Suite generates the child entity by inheriting from Entity (not AggregateRoot). This indicates that the child should be managed under its master (the aggregate root). However, the child entity also gets its own repository, application service, etc., as you noticed.
We designed it this way intentionally. If all child-related operations were included directly in the master’s application service, that service would quickly become large and hard to maintain. Instead, we chose a more practical approach where the child entity has its own repository and application services, while the relationship with the master is still correctly established at the entity and data levels.
So yes, your observation is correct, but this was a deliberate design choice aimed at keeping the generated codebase more manageable. We have made a few adjustments to child entity generation over time, but the overall approach remains the same. That said, your suggestion makes sense, and I’ll create an issue so that we can evaluate it further.
Regards.
