[Franz HonkeParticipant]

Hello Peter Stoev,

will this be realized soon to allow integrity?
I am sure not being the only one requiring this functionality because is essential.

Best regards

Franz Honke

[Franz HonkeParticipant]

Hello Peter Stoev,

I now can iterate object “$(“#scheduler”).jqxScheduler(‘getAppointments’)”. The exceptions details of recurrent appointments can be red by reading “exceptions” object.
Unfortunately there is obviously no way restoring these “exceptions” data so that JQXWIDGET is able to rebuild my scenario!
The field “recurrenceException” is easy to store and restore but the further details not stored at “recurrenceException” are available only at “exceptions” object which seems not being respected by any other appointment data field!

How can this now be handled or fixed?

Many thanks for your support and important hints!
Best regards
Franz Honke

[Franz HonkeParticipant]

Hello Peter Stoev,

thanks for your very quick response!
Unfortunately the “recurrenceException” property does not store any information about one of the modified recurrent appointments (child not parent)! Would you check what happens to a recurrent appointment (parent) after resetting and changing one of it’s recurrence appointments’ propperties (“date” or “location” or …) again?

The “recurrenceException” property obviously will then not be modified. It stores the days which have to be excluded from the series only. My situation stated is not stored here. The modified item itself is not available by “getAppointments” and “getDataAppointments”! The jqxscheduler behaves as if those moved single items from the series are real appointments but they are not available by any methods or functions.

I am able to store this special appointment in the data base but the expected appointment structure is not clear! There is no hint in the documentation solving this at the moment!

Example:
Series1:
Start 20th May 2016,
repeat each day,
whole day
Exception: 22th May 2016, 23th May 2016

After moving 21th May 2016 of this series to 10th May 2016 it is still part of the series but behaves like a new additional appointment! But it is not accessable by the methods of jqxscheduler. Only “appointmentChange” event allows access to this appointment and it’s propperties. I can store this appointment as a new one but it can not be loaded again from the data base and linked to the “parent” appointment again. The widget allways shows those modified as part of the related series but I do now know how to prepare the data source for this!

Best regards

Franz Honke

[Franz HonkeParticipant]

We’re using jQWidgets v4.4.0 (2016-Nov) at the moment.
The jqxscheduler is currently in use. For this I organized storing all appointment data via ajax in data base.
When new appointments are created the appointment ID is created by data base (auto increment integer value) and the dataAdapter is resetted to force a refresh. This allows me to use my own appointment IDs.

This works perfectly until a single appointment of the chain of recurrent appointments is moved outside the chain. The jqxscheduler creates then a new appointment based on the “parent” appointment. It’s ID then is for example “1.1.9a5b3947” while the root appointment’s ID is “1”.

The issue I found is that both functions $(“#scheduler”).jqxScheduler(‘getAppointments’)
and $(“#scheduler”).jqxScheduler(‘getDataAppointments’) don’t supply those “sub” appointments. The only access to these kind of appointments is the “appointmentChange” event after it has been modified.

My questions here are:
1. how to get data of those “sub” appointments as part of the recurrent appointments, too?
2. how to store the data of those “sub” appointments so that it can be reloaded via ajax from the data base and be redrawn? Is there an example that builds this situation from an array data type?

Many thanks for your support

Franz Honke

[Author]

Posts