WebApiAdaptor Error In Schedule

[osama gamal]

public eventSettings: EventSettingsModel= { dataSource: new DataManager({

url: 'https://js.syncfusion.com/demos/ejservices/api/Schedule/LoadData',

crudUrl:'https://js.syncfusion.com/demos/ejservices/api/Schedule/LoadData',

adaptor: new WebApiAdaptor,

})};

I did write the code exactly like the example : https://ej2.syncfusion.com/angular/demos/#/material/schedule/remote-data and this error happened 


ERROR TypeError: Cannot read property 'indexOf' of undefined

    at WebApiAdaptor.push.../node_modules/@syncfusion/ej2-data/src/adaptors.js.UrlAdaptor.processQuery (adaptors.js:462)

    at DataManager.push.../node_modules/@syncfusion/ej2-angular-schedule/node_modules/@syncfusion/ej2-data/src/manager.js.DataManager.executeLocal (manager.js:116)

    at manager.js:164

    at ZoneDelegate.push.../node_modules/zone.js/dist/zone.js.ZoneDelegate.invokeTask (zone.js:421)

    at Object.onInvokeTask (core.js:16126)

    at ZoneDelegate.push.../node_modules/zone.js/dist/zone.js.ZoneDelegate.invokeTask (zone.js:420)

    at Zone.push.../node_modules/zone.js/dist/zone.js.Zone.runTask (zone.js:188)

    at push.../node_modules/zone.js/dist/zone.js.ZoneTask.invokeTask (zone.js:496)

    at ZoneTask.invoke (zone.js:485)

    at timer (zone.js:2054)

[Karthigeyan Krishnamurthi]

Hi Osama,  

 

Thank you for contacting Syncfusion support. 

 

We have checked the reported scenario with the provided code example and Schedule is rendering without any script error. Kindly try the below sample and if the issue persists, try to reproduce the error in a sample and revert else share your Schedule code example/runnable sample (if possible) to serve you better. 

https://stackblitz.com/edit/angular-3pgmgm?file=remote-data.component.ts 

 

Regards, 

Karthigeyan  

[osama gamal]

https://drive.google.com/file/d/1jWVMogHQ_aj_UQ3vsfQ8WiGBCbvWOJLt/view?usp=sharing

just run it in visual studio 2017 and use link  http://localhost:50976/calendar

[Karthigeyan Krishnamurthi]

Hi Osama, 

 

We are happy that your issue is resolved in 2XXXXX ticket. 

 

Regards, 

Karthigeyan