Forum

This screenshot is not informative. It shows request data, not the response.

Issue is resolved and will be released with alpha 3 next week.

Will do.

I opened ticket to investigate this: https://github.com/bryntum/support/issues/1340 Thank you for report. We will try to fix this to alpha 3 (middle of next week)

Actually the array of strings I am converting to string before inserting to db. Hope that step is fine. Model is used in deserializing JSON into class instances. If you want to change field type on the backend you'll have to use two fields: one to serialize/deserialize JSON and other to store data ...

public string ExceptionDates { get; set; } backend expects a string and client passes array of strings. Also why does when we edit second time, that event should have a exception date? It should be null right in the added object? I cannot reproduce this issue on backend demo with recurrence enabled...

Scheduler should've set this height to a container element. So you need to investigate CSS on your page and fix it.

Hello. It looks like a backend issue. Have you added exceptionDates field to the event model? How do you define it?

You can set height on the container element or provide it in config:

Code: Select all

new Scheduler({ height: 100 })

You need to make sure that findRecord fn is avaliable in the scope of the callback. How you do it is up to you, it depends on your app.

Forum

Bryntum Support Forums

Search found 2605 matches

Re: [INFO REQ] [React] - Understanding exceptionDates

Re: gantt-4.0.0-alpha-1 - errors

Re: gantt-4.0.0-alpha-1 - errors

Re: gantt-4.0.0-alpha-1 - errors

Re: [INFO REQ] [React] - Understanding exceptionDates

Re: [INFO REQ] [React] - Understanding exceptionDates

Re: [INFO REQ] Always visible horizontal scroll bar at the top

Re: [INFO REQ] [React] - Understanding exceptionDates

Re: [INFO REQ] Always visible horizontal scroll bar at the top

Re: [ANGULAR] ContextMenu of events