Hello!
I have quite strange issue. I use my own DB for storing scheduler events and this is what I'm facing:
event with RecurrencyRule:
DTSTART:19750312T000000Z
DTEND:19750313T000000Z
RRULE:FREQ=YEARLY;INTERVAL=1;BYMONTHDAY=12;BYDAY=MO,TU,WE,TH,FR,SA,SU;BYMONTH=03
is not showing. Scheduler is set to 2008 march and when I change year to 2007 then event appears. When I change year from 1975 to 1976 then it appears in Scheduler which is set to march 2008 so it looks like this is always the time difference is always the same.
Any ideas?
I have quite strange issue. I use my own DB for storing scheduler events and this is what I'm facing:
event with RecurrencyRule:
DTSTART:19750312T000000Z
DTEND:19750313T000000Z
RRULE:FREQ=YEARLY;INTERVAL=1;BYMONTHDAY=12;BYDAY=MO,TU,WE,TH,FR,SA,SU;BYMONTH=03
is not showing. Scheduler is set to 2008 march and when I change year to 2007 then event appears. When I change year from 1975 to 1976 then it appears in Scheduler which is set to march 2008 so it looks like this is always the time difference is always the same.
Any ideas?
4 Answers, 1 is accepted
0
Accepted
Hi,
This problem has to do with the internal implementation of our recurrence engine. As rules can be quite complex, we create a list of "probable" dates and check if any of them satisfies the complete rule. We are placing a limit of such probable dates, as some of the recurrence rules can be indefinite. When this limit is reached the recurrence engine stops evaluating the rule.
Please, open a formal support ticket, so we can send you the latest build, in which we have increased this limit. We have also introduced a new property on RadScheduler (MaximumRecurrenceCandidates) that you can use to directly control this parameter. The default value should work fine in your case, though.
We are also working on improving our algorithms, so the list of probable dates can be shorter, but still accurate.
Sorry for the inconvenience.
All the best,
Tsvetomir Tsonev
All the best,
Tsvetomir Tsonev
0
GrZeCh
Top achievements
Rank 2
Rank 2
answered on 10 Oct 2008, 01:00 PM
No problem. I just wanted to make sure that You are aware of this. I had submited support ticket.
0
SKS
Top achievements
Rank 1
Rank 1
answered on 23 Mar 2010, 08:33 PM
is there any performance hit if you change the MaximumRecurrenceCandidates = 6000.
by default it is 3000.?
can you please clarify?
by default it is 3000.?
can you please clarify?
0
Hi,
No, there isn't direct performance hit from increasing this number. It simply tells RadScheduler to give up evaluating a recurrence rule after more retries. This mostly affects recurrence rules that span multiple years (over 30 or so). Even for them the performance hit is negligible.
Regards,
Tsvetomir Tsonev
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
No, there isn't direct performance hit from increasing this number. It simply tells RadScheduler to give up evaluating a recurrence rule after more retries. This mostly affects recurrence rules that span multiple years (over 30 or so). Even for them the performance hit is negligible.
Regards,
Tsvetomir Tsonev
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.