Open Closed

Code Generated with error for 2 attribute of IdentityUser Data Type #10941


User avatar
0
johnsonlim created

Hi, This is the error i have

This is IdentityUser Data Type for the attribute

| Attribute | | | --------- | --- | | usermaintenanceUserId | | | supervidorId | |

Markdown supported.
Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

3 Answer(s)
  • User Avatar
    0
    maliming created
    Support Team Fullstack Developer

    Hi,

    When two navigation properties point to the same entity (IdentityUser here), ABP Suite generates the lookup only for the first one in UserMaintenances.razor.cs. The razor page still uses supervisorCollection, so the build fails.

    For now, you can add the missing part to UserMaintenances.Extended.razor.cs. Suite doesn't overwrite this file when you regenerate the page.

    using System;
    using System.Collections.Generic;
    using System.Threading.Tasks;
    using AbpSolution1.Shared;
    
    namespace AbpSolution1.Blazor.Pages;
    
    public partial class UserMaintenances
    {
        private IReadOnlyList<LookupDto<Guid>> supervisorCollection { get; set; } = new List<LookupDto<Guid>>();
    
        protected override async Task OnParametersSetAsync()
        {
            supervisorCollection = (await UserMaintenancesAppService.GetsupervisorLookupAsync(new LookupRequestDto())).Items;
        }
    }
    

    The app service already has GetsupervisorLookupAsync, so nothing else needs to change.

    This is fixed in ABP Suite 10.7.0. After you upgrade Suite and regenerate the page, remove this code from the extended file, because the generated file will have supervisorCollection itself.

    Thanks

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
  • User Avatar
    0
    johnsonlim created

    Hi, I have 2 question as below:

    1. How to do the version update
    2. Will there be impact to the code generated previously
    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
  • User Avatar
    0
    maliming created
    Support Team Fullstack Developer

    Hi,

    Which ABP version is your solution on? The steps below are for upgrading a 10.6.x solution to 10.7.0. If you're on an older version, let me know first.

    1. Commit or back up your work, and close Suite. Then run these in the solution folder:
    abp update --version 10.7.0
    abp suite update --version 10.7.0
    

    abp update doesn't update the other packages your projects reference directly. Align them with ABP 10.7.0, otherwise you can get restore or startup errors. In a Blazor Server solution created with 10.6, these are:

    • Microsoft.AspNetCore.*, Microsoft.EntityFrameworkCore.* and Microsoft.Extensions.* packages: 10.0.9 to 10.0.11
    • Blazorise.Bootstrap5 and Blazorise.Icons.FontAwesome: 2.2.1 to 2.3.0

    The full list is here: https://abp.io/docs/10.7/package-version-changes

    Then check the migration guide: https://abp.io/docs/10.7/release-info/migration-guides/abp-10-7. If app.UseAntiforgery(); comes before app.UseAuthorization(); in your Blazor module, move it after.

    Build the solution, then start Suite again and regenerate UserMaintenance. Suite reads its templates from the built solution.

    1. Updating the packages doesn't change your generated code. Regenerating an entity rewrites the generated files. Keep Customizable code enabled when you regenerate. Suite keeps your code in the extended files and the custom code blocks of the pages, and your texts in the localization files. Changes made directly in other generated code are overwritten, so check the diff after regenerating.

    After you regenerate UserMaintenance:

    • Remove the workaround from UserMaintenances.Extended.razor.cs. The generated page has supervisorCollection now, so keeping it causes a duplicate definition error.
    • If EfCoreUserMaintenanceRepository.cs has using AbpSolution1.using Microsoft.EntityFrameworkCore; and a separate EntityFrameworkCore; line at the top, replace those two lines with:
    using Microsoft.EntityFrameworkCore;
    using AbpSolution1.EntityFrameworkCore;
    

    Then build the solution again and check the page.

    The broken usings come from Suite 10.7.0, and we've already fixed it in the 10.7 branch. If you'd upgrade only for this issue, you can also stay on your current version and keep the workaround.

    Thanks

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
Boost Your Development
ABP Live Training
Packages
See Trainings
Mastering ABP Framework Book
The Official Guide
Mastering
ABP Framework
Learn More
Mastering ABP Framework Book
Made with ❤️ on ABP v10.8.0-preview. Updated on October 30, 2026, 06:34
1
ABP Assistant
🔐 You need to be logged in to use the chatbot. Please log in first.