RadScheduler recursion 'End after x occurrences' bug?

[Sam]

Hi guys,

I'm not sure if this has already been addressed or identified, but I'd like to point out an issue that I can reproduce on your demo page:

Reproduction steps:
1. Go to your demo page: http://demos.telerik.com/aspnet-ajax/scheduler/examples/overview/defaultcs.aspx
2. Click on an available time slot to create an appointment and click 'Options' to bring up the advanced form
3. Give the appointment an arbitrary subject, and check the 'recurrence' box
4. Select and insert '1000' into the 'end after ... occurrences' box
5. Click Save
6. Reopen the appointment ('edit entire series')

Expected results: The 'end after' box still has the value of 1000.
Actual results: The 'end after' box has the value of 1.

Comments:
It works as expected for values up to 999. It seems to run into a problem when the thousands separator comes into play (i.e. the text is formatted as "1,000" when 1000 is entered into the box. As such, I imagine it may have something to do with regional settings and the way numbers are parsed and formatted. At a lower level, it seems that calling:

$find("<recurrenceEditorId>").get_recurrenceRule().get_range().get_maxOccurrences()

returns the incorrect value. Sadly I don't have time to go deeper into the definition of this function, but I would appreciate it if you could kindly let me know:
* Is this indeed a bug?
* Is it a known bug?
* Are there any workarounds?
* Any estimate on when a fix may be released?

Thanks for your time.

Cheers,
Sam

[Boyan Dimitrov]

Hello,

Thank you for contacting Telerik Support.

I am confirming that I have reproduced the described issue and it seems to be a misbehavior. I have already logged it as bug in our system for future fixing. I am afraid that there is no workaround at this moment. I am not able to give you an estimate when a fix will be available, but I would assure you that I will contact you as soon as there is any update regarding that issue.

As a token of gratitude I have updated your Telerik points.

Please apologize for any inconveniences caused.

Regards,
Boyan Dimitrov
the Telerik team

[Boyan Dimitrov]

Hello,

I would like to inform you that a fix for the described issue will be included in the next internal build scheduled for next week .


Regards,
Boyan Dimitrov
the Telerik team

[Sam]

Great! Thanks for updating us on this topic :). It will be helpful for our application (currently under development) when this makes it into an official release/update.