DateRangePicker - Issue editing an existing selected range

When editing an existing range, selecting a new day in one picker of the DateRangePicker unselects the day in the other. To change one end of the range requires three selections. See attached video.

Attachment: 20210409_12h57_26_df5c2572.zip

5 Replies

JC Joseph Christ Nithin Issack Syncfusion Team April 12, 2021 09:03 AM UTC

Hello Michael, 

      Greetings from Syncfusion support.  

     We have checked your query. When a range is already selected, the next date selected acts as the start date, so you have to select both start and end dates again to select a new range. This is the intended behavior of the control. 


Kindly revert us for more queries. 

Regards, 
Joseph Christ nithin Issack. 



MA Michael Aston April 12, 2021 10:00 AM UTC

Not a coding error then but it is poor UI design as amending one end of the range causes the loss of the other end which requires the user to to fix (assuming they remember the other end of the range) before they can update and exit the range picker.

Can the UI design be fixed?




JC Joseph Christ Nithin Issack Syncfusion Team April 13, 2021 02:26 PM UTC

Hello Michael, 

  Thanks for the update. 

    The SfDateRangepicker component is based on a single input where it is difficult to predict the customers input is for the startdate or end date. This would be easily predictable if it is based on two inputs.  
    However, however in scenarios of selecting both the start and the end dates it would be difficult for the users who has to select start date twice, if we make it possible to alter the end date alone as per your request. So it will be appropriate for the users to select both the start and the end date at times of selecting the range, or the user can alter the end date using the input element by typing the end date manually instead of using the calendar to select the dates. 

 Kindly reach us for more queries. 

Regards, 
Joseph Christ Nithin I 



MA Michael Aston April 14, 2021 10:06 AM UTC

A range by definition has a start and end so supporting two inputs would seem appropriate.

Bottom line is that the DateRangerPicker is a poor user experience. The user is not going to engage with or understand your one input justification, rather they just end up frustrated/annoyed.  

Can this be improved?


JC Joseph Christ Nithin Issack Syncfusion Team April 15, 2021 04:36 PM UTC

Hi George,  


Thanks for the update. We have confirmed the requested requirement as an improvement in our end. This support will be included in any one of our upcoming releases. Meanwhile, you can now track the current status of this request, review the proposed resolution timeline, and contact us for any further inquiries through the below link from our feedback portal.   








Regards,  
Joseph Christ Nithin I. 


Loader.
Up arrow icon