[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.
[vu.lang] said: Thanks. Do you have any plans to add support for DateTimeOffset in the near future?
There is no certain date or milestone for supporting the DateTimeOffset type. However, we have an issue for that in the backlog, and in each sprint, we prioritize some features according to your requests.
Hi, ABP Suite does not support DateTimeOffset for now. It supports DateTime, DateOnly, and TimeOnly types for date/time operations.
If ABP Suite does not support, are there any other ways to define the type as DateTimeOffset without manually changing the generated C# code?
Actually, there might be one tricky way to do that in the current structure: You can customize all DateTime templates and change the relevant places to DateTimeOffset type. But this approach might be programmatic, because in your solution then you'll not be able to use the DateTime type, and also schematics might not reflect the changes as expected. Btw, i don't suggest to customize templates for that, but it seems this is the only way for now, and it's really problematic.
Regards.
[rafael.gonzales] said: Not sure if it's related but I see this in the developer tools of the browser when running ABP Suite
Hi, it's not related to that, but this is also something we need to fix. I'll add to the bundle with 9.3.2.
For your main problem, I'll try to reproduce it today, and write back asap. If I'm not able to reproduce it, i may ask your need to send your project via email.
Regards.
Hi, as far as I understand, you said that when customizing an existing template (like Frontend.Mvc.Page.CreateModal.cshtml.txt, for example), it's not applying it correctly. So, to test it out, I've created a new layered MVC application and customized the related template, and the changes are there as expected:
Customized the template from the /Templates page (and simply added a div with a paragraph):
This customization should add a file into your .suite folder:
Here is the generated code:
Did I understand you correctly? Can you check that your template has a customized badge on the templates page or not?
[guven.uysall] said: Hi,
How can we upgrade from 6.0.2 to 9.2 as best practice? Should we follow the migration guide step by step, from 6 to 7, from 7 to 8, and finally from 8 to 9? Or should we just go from 6 to 9?
Hi, starting a step-by-step migration would be better to fix the problems easily. You can check the relevant migration guide after each upgrade: https://abp.io/docs/9.3/release-info/migration-guides/index
