Open Closed

Error encountered while upgrading the project from version 4.3.3 to version 7.0.1 #4719


User avatar
0
ilhan.ordukaya created

Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples, to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, please use the search on the homepage.

If you're creating a bug/problem report, please include followings:

  • ABP Framework version: v4.3.3 - updated v7.0.1
  • UI type: Angular
  • DB provider: EF Core / Mssql
  • Tiered (MVC) or Identity Server Separated (Angular): no
  • Exception message and stack trace:
  • Steps to reproduce the issue:"

"After upgrading the project, the lookup methods in the Pop-up are empty. I initially thought the issue was frontend-related, but it turned out to be API-related. The method being called returns a 500 error code as a response. It was working fine before the upgrade. Could there have been an issue during the upgrade? How can I resolve this?"

I'm waiting for your help.


28 Answer(s)
  • User Avatar
    0
    mahmut.gundogdu created

    it seems "service.getCitylookup" is undefined. Could you check this? Also I have ask team-mate for why backend return 500 too)

    Just a reminder. also there is visual issue. Maybe you should check your styles because some bootstrap classes are deprecated like form-group like padding classes etc.

  • User Avatar
    0
    maliming created
    Support Team Fullstack Developer

    hi

    Method not found

    Can you share some code/project to reproduce it? liming.ma@volosoft.com

  • User Avatar
    0
    ilhan.ordukaya created

    it seems "service.getCitylookup" is undefined. Could you check this? Also I have ask team-mate for why backend return 500 too)

    Just a reminder. also there is visual issue. Maybe you should check your styles because some bootstrap classes are deprecated like form-group like padding classes etc.

    If you want, we can continue in Turkish.

  • User Avatar
    0
    ilhan.ordukaya created

    hi

    Method not found

    Can you share some code/project to reproduce it? liming.ma@volosoft.com

    hi maliming

    "Actually, the error wasn't present in version 4.3.3. It occurred after updating to 7.0.1. It works when using ToListAsync instead of ToDynamicListAsync, but I don't think that's suitable for the look-up method. I believe the problem may be a package mismatch, but it doesn't seem like there's an issue with the ABP packages. There might be a problem with the update. Do you think this could be the case?"

  • User Avatar
    0
    maliming created
    Support Team Fullstack Developer

    hi

    We are using the <PackageReference Include="System.Linq.Dynamic.Core" Version="1.2.18" /> on 7.x

  • User Avatar
    0
    ilhan.ordukaya created

    hi

    We are using the <PackageReference Include="System.Linq.Dynamic.Core" Version="1.2.18" /> on 7.x

    so how can i downgrade this version?

  • User Avatar
    0
    ilhan.ordukaya created

    hi

    We are using the <PackageReference Include="System.Linq.Dynamic.Core" Version="1.2.18" /> on 7.x

    so how can i downgrade this version? I will try thanks

  • User Avatar
    0
    maliming created
    Support Team Fullstack Developer

    You can try to add <PackageReference Include="System.Linq.Dynamic.Core" Version="1.2.18" /> to your project.

  • User Avatar
    0
    maliming created
    Support Team Fullstack Developer

    If other projects refer to high-version packages, you can only wait for abp to upgrade

  • User Avatar
    0
    mahmut.gundogdu created

    it seems "service.getCitylookup" is undefined. Could you check this? Also I have ask team-mate for why backend return 500 too)

    Just a reminder. also there is visual issue. Maybe you should check your styles because some bootstrap classes are deprecated like form-group like padding classes etc.

    If you want, we can continue in Turkish.

    I can understand Turkish, but Maliming is is not. . but if you can write English. Lets continue in English or I would translate Turkish to Eng

  • User Avatar
    0
    ilhan.ordukaya created

    If other projects refer to high-version packages, you can only wait for abp to upgrade

    "Actually, the project is created with the ABP Suite. Should I wait for ABP to be upgraded for this?

  • User Avatar
    0
    maliming created
    Support Team Fullstack Developer

    "Actually, the project is created with the ABP Suite. Should I wait for ABP to be upgraded for this?

    OK, How can I reproduce this exception?

    Please share the steps and code. Thanks

  • User Avatar
    0
    ilhan.ordukaya created

    "Actually, the project is created with the ABP Suite. Should I wait for ABP to be upgraded for this?

    OK, How can I reproduce this exception?

    Please share the steps and code. Thanks

    "Actually, I don't think the error can be reproduced because I created a project that also includes the look-up method with ABP Suite, and that method works fine there. What do you think I should pay attention to when upgrading the project from dotnet5.0 to dotnet7.0?"

  • User Avatar
    0
    maliming created
    Support Team Fullstack Developer

    Please refer to our upgrade documentation,

    https://docs.abp.io/en/abp/latest/Migration-Guides/Index https://docs.abp.io/en/commercial/latest/migration-guides/index

    It is difficult for me to determine the cause of the problem if I cannot reproduce the problem

  • User Avatar
    0
    ilhan.ordukaya created

    Please refer to our upgrade documentation,

    https://docs.abp.io/en/abp/latest/Migration-Guides/Index https://docs.abp.io/en/commercial/latest/migration-guides/index

    It is difficult for me to determine the cause of the problem if I cannot reproduce the problem

    Actually, we can maybe replicate the error by creating a branch of a project with version 4.3.3 that has the lookup method and upgrading it to 7.0.1 to obtain the error

  • User Avatar
    0
    maliming created
    Support Team Fullstack Developer

    OK, I'll wait for your project. liming.ma@volosoft.com

  • User Avatar
    0
    ilhan.ordukaya created

    OK, I'll wait for your project. liming.ma@volosoft.com

    The 500 error that was caused by a backend issue has been resolved with the help of @gterdem 's support. Thank you for your assistance. But the front-end issue still persists. @mahmut.gundogdu

  • User Avatar
    0
    maliming created
    Support Team Fullstack Developer

    ok I will ask mahmut.gundogdu

  • User Avatar
    0
    mahmut.gundogdu created

    OK, I'll wait for your project. liming.ma@volosoft.com

    The 500 error that was caused by a backend issue has been resolved with the help of @gterdem 's support. Thank you for your assistance. But the front-end issue still persists. @mahmut.gundogdu

    I have produced the issue. getFn ="" must be input. it is not output.

  • User Avatar
    0
    ilhan.ordukaya created

    OK, I'll wait for your project. liming.ma@volosoft.com

    The 500 error that was caused by a backend issue has been resolved with the help of @gterdem 's support. Thank you for your assistance.But the front-end issue still persists. @mahmut.gundogdu

    I have produced the issue. getFn ="" must be input. it is not output.

    i am getting an error like this @mahmut.gundogdu

  • User Avatar
    0
    mahmut.gundogdu created

    I think expected signature is different here the signeture of getFn

    getFn: (params: ABP.PageQueryParams) => Observable<ABP.PagedResponse<any>>;
    

    PageQueryParams is

     interface PageQueryParams {
            filter?: string;
            sorting?: string;
            skipCount?: number;
            maxResultCount?: number;
        }
    

    lookupRequestDto is not compatible PageQueryParams maybe you should wrap this with a file or maybe you should re-generate the proxies.

  • User Avatar
    0
    ilhan.ordukaya created

    I think expected signature is different
    here the signeture of getFn

    getFn: (params: ABP.PageQueryParams) => Observable<ABP.PagedResponse<any>>; 
    

    PageQueryParams is

     interface PageQueryParams { 
            filter?: string; 
            sorting?: string; 
            skipCount?: number; 
            maxResultCount?: number; 
        } 
    

    lookupRequestDto is not compatible PageQueryParams maybe you should wrap this with a file or maybe you should re-generate the proxies.

    Mahmut bey dediğiniz interfacelere ve sınıflara baktık herhangi bir farklılık göremedik konuyla ilgi uygun bir zamanınızda zoom üzerinden bir toplantı gerçekleştirebilirmiyiz?

  • User Avatar
    0
    ilhan.ordukaya created

    I think expected signature is different
    here the signeture of getFn

    getFn: (params: ABP.PageQueryParams) => Observable<ABP.PagedResponse<any>>;  
    

    PageQueryParams is

     interface PageQueryParams {  
            filter?: string;  
            sorting?: string;  
            skipCount?: number;  
            maxResultCount?: number;  
        }  
    

    lookupRequestDto is not compatible PageQueryParams maybe you should wrap this with a file or maybe you should re-generate the proxies.

    Mahmut bey dediğiniz interfacelere ve sınıflara baktık herhangi bir farklılık göremedik konuyla ilgi uygun bir zamanınızda zoom üzerinden bir toplantı gerçekleştirebilirmiyiz?

    mahmut bey merhaba sorun hala devam ediyor nasıl çözüme ulaştırabiliriz?

  • User Avatar
    0
    mahmut.gundogdu created

    Hocam lookuprequestDTO nun icerigini paylasabilir misniz? Bir de service.getLookupCity foksiyonunun imzasini ve imzadaki typelari paylasabilir misiniz? bir type uyumsuzlugu var. olmadi seklinde fonsiyon olusturup sorunu .html den en azindan .ts e tasisak. orada daha rahat type cast yapaibliriz.

    getCityData(input:PageQueryParams){
     return this.service.getCityLookup(input)
    }
    
  • User Avatar
    0
    ilhan.ordukaya created

    getCityData(input:PageQueryParams){ return this.service.getCityLookup(input) }

Made with ❤️ on ABP v8.2.0-preview Updated on March 25, 2024, 15:11