Activities of "EngincanV"

[Prinay] said: Hi EngincanV,

Your recommendation worked perfectly. I have renamed the entity to not match the project name and it generated perfectly.

I will note this going forward. The DownloadTokenResultDto error is also gone. I suspect it was the conflicting namespace too as you mentioned.

Thanks for the assistance.

Hi @Prinay, I'm happy to help.

Best regards.

[Prinay] said: Additional context.

If I create related entities with Create user interfaces checked I run into even more issues.

Again, I have made 0 customisations and this is just pure generation at this point.

Hi Prinay,

It seems the error is caused by the project name and entity name being the same. To help us reproduce the issue, could you share your solution via email to support@abp.io with your ticket number? If that's not possible, please let me know and I'll try to reproduce it using the configurations you've provided above.

Also, could you confirm whether you have a DTO class called DownloadTokenResultDto and that its namespace is different from Payments.Shared?

Best regards.

Hello again, we have fixed the problem and it's under review now. Once, it's reviewed and we release a new version for v10.1, it will be available:

I refunded your ticket and since the work is under review and planned to be included in the next patch release, I close the question.

Best regards.

Hi @improwise, I'll create an issue and fix it asap. (Your ticket is refunded)

Best regards.

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.