1. Home
  2. Forum
  3. Angular - EJ 2
  4. Does syncfusion 18.3.x support angular 11.0.x?

Does syncfusion 18.3.x support angular 11.0.x?

After updating the system to the latest version of Syncfusion, Angular and .net Core, it seems that some controls no longer work.

Specifically I am referring to syncfusion.grid which is formatted with the correct number of lines but empty and to reactForm which is also formatted / validated correctly but the fields are empty.

My Visual Studio 2019 project is: 
     .NET 5.0 framework

My current installation is:
Angular CLI: 11.0.1
Node: 14.15.1
OS: win32 x64

Angular:
...
Ivy Workspace:

Package                      Version
------------------------------------------------------
@angular-devkit/architect    0.1100.1 (cli-only)
@angular-devkit/core         11.0.1 (cli-only)
@angular-devkit/schematics   11.0.1 (cli-only)
@schematics/angular          11.0.1 (cli-only)
@schematics/update           0.1100.1 (cli-only)

My current package.json
  "private": true,
  "dependencies": {
  "@angular/animations": "11.0.1",
  "@angular/cdk": "^11.0.0",
  "@angular/common": "11.0.1",
    "@angular/compiler": "11.0.1",
    "@angular/core": "11.0.1",
    "@angular/flex-layout": "^11.0.0-beta.33",
    "@angular/forms": "^11.0.1",
    "@angular/http": "^7.2.16",
    "@angular/material": "^11.0.0",
    "@angular/platform-browser": "11.0.1",
    "@angular/platform-browser-dynamic": "11.0.1",
    "@angular/platform-server": "11.0.1",
    "@angular/router": "11.0.1",
    "@nguniversal/module-map-ngfactory-loader": "8.1.1",
    "@syncfusion/ej2-angular-base": "^18.3.47",
    "@syncfusion/ej2-angular-buttons": "^18.3.47",
    "@syncfusion/ej2-angular-calendars": "^18.3.48",
    "@syncfusion/ej2-angular-charts": "^18.3.50",
    "@syncfusion/ej2-angular-dropdowns": "^18.3.48",
    "@syncfusion/ej2-angular-grids": "^18.3.50",
    "@syncfusion/ej2-angular-inputs": "^18.3.48",
    "@syncfusion/ej2-angular-lists": "^18.3.47",
    "@syncfusion/ej2-angular-navigations": "^18.3.50",
    "@syncfusion/ej2-angular-notifications": "^18.3.47",
    "@syncfusion/ej2-angular-popups": "^18.3.50",
    "@syncfusion/ej2-angular-splitbuttons": "^18.3.50",
    "aspnet-prerendering": "^3.0.1",
    "bootstrap": "^4.3.1",
    "core-js": "^3.3.3",
    "jquery": "3.4.1",
    "oidc-client": "^1.9.1",
    "popper.js": "^1.16.0",
    "rxjs": "^6.5.3",
    "tslib": "^2.0.0",
    "zone.js": "~0.10.2"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "~0.1100.2",
    "@angular/cli": "^11.0.2",
    "@angular/compiler-cli": "^11.0.1",
    "@angular/language-service": "^11.0.1",
    "@types/jasmine": "~3.6.0",
    "@types/jasminewd2": "~2.0.8",
    "@types/node": "^12.11.1",
    "codelyzer": "^6.0.0",
    "jasmine-core": "~3.6.0",
    "jasmine-spec-reporter": "~5.0.0",
    "karma": "~5.1.1",
    "karma-chrome-launcher": "~3.1.0",
    "karma-coverage-istanbul-reporter": "~3.0.2",
    "karma-jasmine": "~4.0.0",
    "karma-jasmine-html-reporter": "^1.5.0",
    "typescript": "4.0.5"
  },
  "optionalDependencies": {
    "node-sass": "^4.12.0",
    "protractor": "~7.0.0",
    "ts-node": "~8.4.1",
    "tslint": "~6.1.0"
  }


Thanks for your answer.
Lino

3 Replies 1 reply marked as answer
TS Thiyagu Subramani Syncfusion Team November 24, 2020 01:16 PM UTC

Hi Tabular, 

Thanks for contacting Syncfusion forum. 

Based on your shared information we suspect that while you updating packages as latest version, you facing some controls are works no longer. So we have to know which are the controls you facing this issue. 

Query: Syncfusion Grid which is formatted with the correct number of lines but empty and to reactForm which is also formatted / validated correctly but the fields are empty. 
 
Based on the shared information we suspect the reported problem might be occurring due to one of the following reasons, 

  • The field names bound in the Grid columns does not match those in the Grid data. So can you please ensure this case from your end.
  • If you are using ASP.NET Core then it might be occurring due to serialization problems. If so, this can be resolved by adding DefaultContractResolver in Startup.cs file.

If the ASP.NET CORE version is 2.X then the below code needs to be added in the startup.cs file of the application 

public void ConfigureServices(IServiceCollection services) 
{ 
    services.AddMvc().AddJsonOptions(options => 
    { 
        options.SerializerSettings.ContractResolver = new Newtonsoft.Json.Serialization.DefaultContractResolver(); 
    }); 
} 
 
If the ASP.NET CORE version is 3.X then add the below code in startup.cs file 
 
public void ConfigureServices(IServiceCollection services) 
{ 
    services.AddMvc().AddNewtonsoftJson(options => 
    { 
        options.SerializerSettings.ContractResolver = new DefaultContractResolver();
    });  
} 

Please check the below documentation link for more details on this, 


If you still facing the issue please share image representation of this issue with brief explanation. 

Please get back to us, if you need any further assistance. 

Regards, 
Thiyagu S 


Marked as answer
TA Tabular November 24, 2020 07:51 PM UTC

Grazie, risolto.

Mancava proprio:
            services.AddMvc().AddNewtonsoftJson(options =>
            {
                options.SerializerSettings.ContractResolver = new DefaultContractResolver();
            });"

Ciao
Lino

TS Thiyagu Subramani Syncfusion Team November 25, 2020 09:04 AM UTC

Hi Tabular, 

Thanks for your update. 

We are happy to hear that the provided solution works at your end. 

Please get back to us, if you need any further assistance. 

Regards, 
Thiyagu S 


Loader.
Up arrow icon