Scheduler not working with UrlAdaptor - From 186696

[Chris Franz]

Just discovered a few more issues with using the DefaultContractResolver. First off the scheduler control does not render data when the contract resolver is defined. Second it changes the way that parameters are passed back to JAVA in the args.rowData.

For example without the contract resolver parameters come back in camel case with the first letter always in lower case. With the contract resolver defined the exact name of the parameter comes back. So if one of the columns in my data is named EventId with the contract resolver this is parsed to EventId without the contract resolver it becomes eventId.

Not a huge deal but since JAVA is case sensitive this ended up breaking several of my scirpts where I needed to retrieve a value from a row. 

 // Works if contract resolver is not defined
value= args.rowData.eventId 
 // Must be changed to this with contract resolver
 value= args.rowData.EventId 

 I understand that the behavior is different just wanted to point this out. Also any ideas on why the UrlAdapter stopped working with the scheduler let me know.

Chris 

[Saritha Sankar]

Hi Chirs Franz,

We maintain Pascal casing for the EventSettings.DataSource by default. When using a ContractResolver, the data is automatically converted to proper Pascal casing, ensuring the Schedule component renders correctly.

If you prefer not to use the ContractResolver, you can still achieve correct rendering by applying camel casing using the e-field mappings according to your use case. This approach will also ensure that data binds properly. Refer the below code for your reference.
 

<ejs-schedule id="schedule" width="100%" height="550" selectedDate="new DateTime(2017, 6, 5)">

    <e-schedule-eventsettings dataSource="dataManager">

        <e-eventsettings-fields id="id">

            <e-field-subject name="subject"></e-field-subject>

            <e-field-isallday name="isAllDay"></e-field-isallday>

            <e-field-starttime name="startTime"></e-field-starttime>

            <e-field-endtime name="endTime"></e-field-endtime>

        </e-eventsettings-fields>

    </e-schedule-eventsettings>

</ejs-schedule>

Documentation link: Appointments in ASP.NET CORE Syncfusion Schedule Component

Kindly refer to the Network tab in the attached image and check the casing format. If the field names in e-field match the response casing, the Schedule will function as expected.

Please let us know if you need any further assistance.

Regards,

Saritha S.