Hi @granade, please ignore the response from the AI bot.
As you stated, the only difference between the generated code and your existing mapping code is the trailing “s” in the class name. If, in your existing code, you rename the class names and add a trailing “s” to them, ABP Suite should recognize that the mapping already exists and should not add a new mapper class.
ABP Suite performs a regular expression (regex) check on the class name and the inherited class structure; currently, it does not find a match due to the missing “s” at the end of the mapping class name.
[hassan.abuhelweh] said: Thanks for the update looking forward to it
Hi, it should be fixed with v10.0.3. If you want you can update your solution to v10.0.3 (and also ABP Suite) and give it a try.
Best regards.
[improwise] said: Actually, I thought so to but turns out they properties are actually included all the way, at least with the Angular UI we are using. All you need to do is to fix the last step to actually have them show up. This is at least true for the list (GetList), have not looked if they are included for Get(xxx) as well.
<ngx-datatable-column name="{{ '::CreationTime' | abpLocalization }}" prop="measurementAssignment.creationTime" > <ng-template let-row="row" ngx-datatable-cell-template> {{ row.xxx?.creationTime | shortDateTime }} </ng-template> </ngx-datatable-column>
I dont know the Angular UI, but will share this feedback with our Angular team, and let you know.
Hi, currently ABP Suite does not automatically include base-class properties (auditing fields, and other fields) into the generated DTOs/pages, and to be honest we haven't consider this previous and don't have an open issue for that. I'll create an issue to consider that and we'll try to prioritize it. (Adding an option for that seems valuable, so I will discuss this with the team and we will consider to implement for the near feature)
Best regards.
Hi, I've reproduced the problem just before and will create an issue to fix it. It will be probably included in the patch release and I've refunded your question credit. In the meantime, you can manually fix the problem. Sorry for the problem and we will fix it asap.
Best regards.
[hassan.abuhelweh] said: Hello Any update on this ticket. Please help
Hi, we have fixed the problem and it will be included with the patch release. So, we should wait for the patch release.
Regards.
Hi again, I have tried it and it did not work as you said. I've created an issue for that and we will fix this problem asap. (I refunded your ticket)
Regards.
[hassan.abuhelweh] said:
Hello @EngincanV
Please advice, we are stuck for the last 4 days
I'll test it today and let you know.
[hassan.abuhelweh] said: I found the file but and I added the .dll but still not working
{ "Modules": [ { "DomainProjectDllFileName": "Persona.MasterData.Domain.dll" } ] }Please advise quickly because we are stuck and time wasted
Hi, can you explain the problem? Does it not list the entities from the domain project or does it list it but when you try to establish 1 to n, then it creates build problems etc... ?
[hassan.abuhelweh] said: I found the file but and I added the .dll but still not working
{ "Modules": [ { "DomainProjectDllFileName": "Persona.MasterData.Domain.dll" } ] }Please advise quickly because we are stuck and time wasted
Does the Persona.Enrollment project have dependency to the relevant domain package? Probably not and it seems this is the reason. You should ensure that and try again, it should work but if you get problem, let me know.
Regards.
