I have a RadScheduler instance on a DNN UserControl. The back end of the control feeds data called Alerts into the scheduler. Most alerts are intended to be recurring, usually once a week or semi-weekly, etc.
As you can see in the block, I have default Monthly view and how we do add/edit options etc. The end result of how the Alert (Appointment) looks on the calendar days themselves is a red or green square followed by the name (cut off if the name is too long to fit in the box). You click the Alert to open a custom editor. The choice between Red and Green square is based on a 'Completed Reccurences' list for the user which says that for a given Alert, recurrence indexes X,Y,Z are Completed if they are present in that Completed list. Completed are Green, the rest are Red.
Now all of this has been working to set up recurrences by generating the rules, etc. and we just now figured out that the Recurrence Indexes are based on the Monthly View that you are currently looking at. We were expecting that if something started on X date and recurred weekly, then 2 months later the indexes should be somewhere like 8-12, but they are not.
For instance, we have a recurrence set to start on Friday, July 3rd on a weekly basis. It shows up every Friday like intended. The user has 'completed' the Recurrences that are on the 3rd, 10th, 17th and 24th of July (these are in green), but not the 31st (this one is in red). That is all working as expected.
However, we jump to the next month, August. No recurrences have been completed for this month (since that is in the future) and here is what we see:
The indexes, starting from July 31st (the fifth instance) are reset to start from 0. Since I have 'Completes' recorded for "",0,1,2 it's marking those as complete in the UI. However since these are instances that should be starting with "3" on the 31st, I should be seeing 3,4,5,6,7 in the month of August.
If this were related to what Month it was, where in the index was reset at the beginning of the month and the 7th of August (the first Friday to contain the Alert), I could handle that by adding the Month to my database and call it part of the unique id. But with it based on whatever view the user is looking at I can't reliably do that.
What can I do to fix this? I need permanent indexing based on when the recurrence rule actually started, not based on the view the user is looking at on the page.